Update of bug #32765 (project xnee):
Item Group: None => Error report
Status: None => Works For Me
_______________________________________________________
Follow-up Comment #1:
I am pretty sure this is the same as in the FAQ entry:
‘Xnee seems to mess up my entire session after replaying a sessions which
was interupted by Control-C?’
Xnee records the KeyPress belonging to Control. After that the system
sends Xnee a signal which makes Xnee stop recording. So you end up having a
Control KeyPress recorded, with no coresponding KeyRelease. To solve the
screwed up session, press Control (which generates a KeyPress and the wanted
KeyRelease). If you want to keep your recorded session and not want this to
happen again, remove the last line in the recorded file starting with 2,.
A better way to interrupt Xnee is to use the stop key option, e.g in cnee
--stop-key F1. This prevents the above situation.
GNU Xnee FAQ: http://itupw056.itu.chalmers.se/xnee/doc/xnee.html#FAQ
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?32765>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-xnee mailing list
Bug-xnee@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-xnee
