bug-xnee
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-xnee] [bug #36662] 2 extra lines, not really needed, printed to rec


From: anonymous
Subject: [Bug-xnee] [bug #36662] 2 extra lines, not really needed, printed to recorded log files
Date: Thu, 28 Jun 2012 09:28:23 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20100101 Firefox/10.0.4 Iceweasel/10.0.4

Follow-up Comment #4, bug #36662 (project xnee):

Thank you very much for working on the fix.

> Replaying XI event without XI does not work - really dunno if this is
necessary to implement.... who records on an XI device and then replay on a
non XI device?

At least I do. In my not yet published xnee-based project for
recording/replaying macros, recorded files supposed to be portable. At this
moment, recorded xnee XI log is not portable at all - if a device (identified
by its ID) is not present, cnee will just crash, even if the actual device is
still present (BTW, device name is more reliable way to check a presence
device and discover its current ID). There is bug 36663 for this problem, but
its about fixing a crash, not making XI logs portable. At this moment I use
hackish preprocessing script to convert XI events to X events on the fly. This
is awkward and should not be necessary in my opinion.

I think it makes sense to record XI events in order to preserve as much useful
information as possible (for example, for per device statistics or for more
post-filtering possibilities) and be able to replay recorded events with
--force-core-replay no matter what XI devices are present or what their IDs
are. Without this option, recorded XI logs may be useless even on the same
computer just because some IDs changed or some devices were removed.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?36662>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]