[Bug-xnee] Re: Scriptable Event Log? WAS: replicated event is ahead of the application

[Henrik Sandklef]

On Fri, 2003-06-20 at 04:27, Ariz Jacinto wrote:
> 
> Henrik Sandklef wrote:
> > What more do you expect than to be replayed than the mouse motions?
> 
> 
> i just want the time differences between button presses also be
> replayed  =)

According to your log files there are no 'button press events' recorded.
You haven't specified Xnee to do so either....

Again:
------
 What device, device driver etc do you use to generate the ButtonPress
X11 events?

 What X extension do you use if the device is needed an extension?








> 
> 
> my reasons for doing this? 
> 
> - varying machine performance.
>     
>     you simply can't replay an event log that have been 
>     recorded from a faster machine on a slower one. 
>     doing it the other way around would have solved it but
>     will result to inefficiency.

It is intended to be so in the future.... 

> 
> - laziness
> 
>     i don't have the patience to record a set of 100 buttonpresses 
>     repeatedly (x1000?). "cut & paste"-ing the event log would have 
>     solved it but will result to a much larger log which is not necessary.

A script plugin to Xnee is very interesting and has been thought of much
lately. A loop construct will be one of the first to to add.

> 
> - pride
> 
>     they're doing it on M$ so can Xnee!!!   =)

no comments ;)

> 
> 
> 
> hindrance i've encountered so far:
> 
>     i don't know which of the log entries is for this & that.
>     the "-pens" doesn't seem to work on me and so is "-sk".
>     bug or anything that i've missed?

 -pens requests Xnee to print out the name of the events
 this option is the samt as 
 --print-event-names
This option works fine for me. Please explain what doesn't work.


 -sk set the stop key/modifier.
Example:
   -sk Control,d
will make Xnee break when the Ctrl key and the 'd' key is pressed at the
same time.



> 
> 
> Thanks & Xnee rocks!!!
> 
:)


regards, hesa
> 
>