Re: [rudalics@gmx.at: Re: [simon.marshall@misys.com: mouse-autoselect-window needs a de lay]]

[martin rudalics <rudalics@gmx.at>]

 > To me it makes more sense if this "move and stop" is the default method
 > (ie. selected with a positive delay value).  The negative value could
 > be for experts which want just the move delay.

The absolute value of the delay is used to set up a timer whenever the
mouse crosses a window border.  Usually though, the mouse pointer
already appears at a completely different position at the moment I
install the timer.  Unfortunately, I can't access that position easily.

When the timer triggers I do (provided other conditions apply as well)

- for a positive delay select the window,

- for a negative delay check whether mouse-position is the same as the
   last time I checked.

Now, the very first "last time I checked" occurs at the window border as
I explained above.  Hence the first time the timer fires, the recorded
mouse-positions are usually _not_ equal and I have to restart the timer
until they are.  In practice this means that if I set the delay to -1
and move to the center of another window in a single stroke, the window
is selected after 2 seconds which is more than 1 seconds after the mouse
stopped moving.  Since this is slightly counterintuitive I wouldn't want
to make that the default.

 > But why not separate the two timeout settings, e.g. make it a cons with
 > the "move delay" in the car and "stopped delay" in the cdr.  That's
 > easy to set via customize.

Currently, there is only one delay.  Do you think I should use two
different delays?