xnee-devel
[Top][All Lists]
Advanced

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

Re: [Xnee-devel] Xnee and relative mouse positions


From: Henrik Sandklef
Subject: Re: [Xnee-devel] Xnee and relative mouse positions
Date: Tue, 07 Aug 2007 09:02:02 +0200
User-agent: Mozilla-Thunderbird 2.0.0.4 (X11/20070622)

hi, and thanks for your report

Mads Lindstrøm wrote:
> Hi all
> 
> I have tried to use Xnee for recording and replaying events. But if the
> window is not in the same position when I record events, as when I
> replay the events, then the replay do not go as expected. I tried using
> the --recall-window-position option, but it did not help.


That's strange. Is the window created during recording/replying or does
it exist before?

If created during recording, use:
  --recall-window-position

if not, use:
   --xnee_replay_offset
   (will be renamed to '--replay-offset' in coming 3.0.2)



> It seems that Xnee is recording absolute mouse positions. If Xnee
> recorded them relative to the window that the mouse pointer was located
> within, it would not matter if a window did not have the same position
> when recording and replaying the events. E.g. I would like Xnee to store
> both the mouse position relative to the window which the mouse pointer
> is located within and the title of this window. Then when the events are
> replayed, Xnee should search for a window with the recorded title, make
> it active, and move the mouse pointer relative to the window which it
> had just made active. This would eliminate the problem mentioned above.

It would be hard to implement and I am not sure it's worth it. What
window events should belong to what windows. Let's say that we move the
mouse over a window while recording. During replay you say we make the
window active (by clicking?). Then we interfere with the recorded session.

I think there's another problem with your proposal (correct if I am
wrong!!!). Let's say we have two windows there were created during
recording, A and B. Window A was created first and B second. So when we
replay Window B is created first since something strange happened that
slowed down A. Now, we'll end up with A's events being replayed to B and
vice versa.

- Wouldn't he same thing will happen with --recall-window-position?
Yes :(



> Would my solution be possible?

Not sure. I may lack coffee at the moment (actually I need to put on
some more) so I may be wrong :)

> Would my solution be desirable or I am just missing something?

A solution is desirable... so let's keep talking until we find one!



/hesa




reply via email to

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