xwrits (2.21-6.1) debian-changes-2.21-6.1

Summary

 rest.c     |    8 ++++++++
 schedule.c |    1 +
 xwrits.1   |    4 ++--
 3 files changed, 11 insertions(+), 2 deletions(-)

    
download this patch

Patch contents

Description: Upstream changes introduced in version 2.21-6.1
 This patch has been created by dpkg-source during the package build.
 Here's the last changelog entry, hopefully it gives details on why
 those changes were made:
 .
 xwrits (2.21-6.1) unstable; urgency=low
 .
   [ Jari Aalto ]
   * Non-maintainer upload.
     - Move to packaging format "3.0 (quilt)".
   * debian/clean
     - Mew file.
   * debian/compat
     - New file.
   * debian/control
     - (Build-Depends): update obsolete xutils to xutils-dev.
       (important; Closes: #579038). Remove *-1 version suffix
       from texinfo dependency. Update to debhelper 7.1.
     - (Depends): add ${misc:Depends}.
     - (Homepage): New field.
     - (Standards-Version): update to 3.8.4.
   * debian/copyright
     - Update layout and point to GPL-2.
   * debian/rules
     - Delete EOL whitespaces.
     - (DH_COMPAT): Remove.
     - (install): Update dh_clean to dh_prep.
     - (clean): Fix lintian debian-rules-ignores-make-clean-error.
   * debian/source/format
     - New file.
   * debian/watch
     - New file.
   * xwrits.1
     - Fix hyphens.
 .
 The person named in the Author field signed this changelog entry.
Author: Jari Aalto <jari.aalto@cante.net>
Bug-Debian: http://bugs.debian.org/579038

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: <vendor|upstream|other>, <url of original patch>
Bug: <url in upstream bugtracker>
Bug-Debian: http://bugs.debian.org/<bugnumber>
Forwarded: <no|not-needed|url proving that it has been forwarded>
Reviewed-By: <name and email of someone who approved the patch>
Last-Update: <YYYY-MM-DD>

--- xwrits-2.21.orig/schedule.c
+++ xwrits-2.21/schedule.c
@@ -273,6 +273,7 @@ loopmaster(Alarmloopfunc alarm_looper, X
 	       || root_y < ports[i]->last_mouse_y - mouse_sensitivity
 	       || root_y > ports[i]->last_mouse_y + mouse_sensitivity) {
 	     XEvent event;
+	     memset(&event, 0, sizeof(event));
 	     event.type = MotionNotify; /* skeletal MotionNotify event */
 	     if (x_looper && ports[i]->last_mouse_root)
 	       ret_val = x_looper(&event, &now);
--- xwrits-2.21.orig/xwrits.1
+++ xwrits-2.21/xwrits.1
@@ -68,7 +68,7 @@ for 10 minutes.
 Any options preceding an \fBafter\fP option also apply following it, unless
 you explicitly cancel them. For example:
 .nf
-	xwrits +finger after=10 -finger
+	xwrits +finger after=10 \-finger
 .fi
 .PP
 Multiple \fBafter\fP options create a series of escalations. \fIDelay\fP
@@ -308,7 +308,7 @@ Here is the way I run xwrits:
 .fi
 This looks pretty spectacular:
 .nf
-	xwrits t=0 b=:2 f fla=:.5 m=:.31 max=100 -i
+	xwrits t=0 b=:2 f fla=:.5 m=:.31 max=100 \-i
 .fi
 Whee!!
 '
--- xwrits-2.21.orig/rest.c
+++ xwrits-2.21/rest.c
@@ -12,9 +12,17 @@ static int
 wait_x_loop(XEvent *e, const struct timeval *now)
 {
   struct timeval diff;
+
+
+    // patch to get xwrits to ignore all synthetic events, provided by
+    // Roderick Schertler, 2005
+    if(e->xany.send_event) 
+    return 0; //whatever tran_rest means it ignores the event
   
   if (e->type == KeyPress || e->type == MotionNotify
       || e->type == ButtonPress) {
+      
+
     xwSUBTIME(diff, *now, last_key_time);
     last_key_time = *now;