Well, what you are witnessing is an artifact of how X manages cursors.
When you have a cursor what you have is a square either 32x32 or 64x64
depending on your Xserver. When you define some graphic to be your
cursor in the bitmap you define a hotspot. That is to say given this
large square moving about the screen X events are looking for a single
pixel as the cursor location and that is the hotspot. What unclutter
does is replaces your cursor with a masked square and for good or bad it
uses the upper left I believe as the hotspot (the default).
So if your cursor is on the edge of a window and then morphs to a square
your cursor position may change as far as X is consered. So whether
this is a bug or not and where it is entirelly up to your desires and
to an extent your fvwm focus policy. I'm a sloppy focus kind of guy,
and have happily used unclutter for going on 4yrs yes I just checked my
binary mod time and it has been 4yrs. The proper fix would be to get
the current hotspot just before masking your cursor and then placing the
hotspot in the same place in the "invisible cursor". Of course this fix
would go in unclutter and since I haven't seen and update in ages nor do
I recall who wrote it my suggestion would be to find someone motivated
to fix it. Or to use this as an opportunity to learn some X code.
Brad
On Tue, Sep 12, 2000 at 06:16:11PM +0100, Joseph Manning wrote:
> Hello,
>
> I'm running FVWM-2.3.22 under RedHat Linux 6.0.
>
> I'm also running the nice little 'unclutter' utility:
>
> http://rpmfind.net/linux/RPM/contrib/libc6/i386/unclutter-0.8-4.i386.html
>
> which makes the cursor vanish after a short period of inactivity.
>
> However, 'fvwm' and 'unclutter' have a small problem interacting with
> one another --- if the cursor is on the side border of a window,
> and 'unclutter' has made it vanish, then pressing a key which has
> a 'Key' binding does not actually invoke that binding; instead,
> it just echoes that key into the window.
>
> For example, with the binding:
>
> Key m FSTW M Maximize 100 100
>
> pressing Alt-m when the cursor is on the side border and has vanished
> simply causes the letter 'm' to be typed in the window, rather than
> resulting in the window being maximized. If Alt-m is pressed before
> the cursor has vanished, then the window is indeed maximized.
>
> The problem remains even when 'Key' is changed to 'PointerKey',
> and under both 'MouseFocus' and 'SloppyFocus'.
>
> Even after the cursor vanishes, the given window STILL RETAINS FOCUS;
> its borders are still highlighted, and the keys which are pressed
> are echoed into it.
>
> I do not know if the problem lies with 'unclutter' or with 'fvwm'.
> I read through the 'unclutter' source code, but I know very little
> about the details of X-windows programming, so I could not spot anything.
>
> Finally (!) my questions: has anyone else come across this problem,
> and does anyone have a work-around to it?
>
> If the window still has focus, should it not correctly process the key?
>
> Thanks for listening!
>
> Cheers, Joseph
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph Manning / Computer Science / University College Cork / manning_at_cs.ucc.ie
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
--
--- There are two kinds of knowledge, you either know the answer or
you know where to find it
-Kane, Johnson, and anonymous
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Sep 12 2000 - 20:21:38 BST