Re: FVWM: warping pointer w/ XFree86 4.0 + Xinerama

From: Danny Dulai <nirva_at_ishiboo.com>
Date: 16 Mar 2000 07:37:52 -0000

On 03/16/00, Dominik Vogt said:
>On Thu, Mar 16, 2000 at 05:55:00AM -0000, Danny Dulai wrote:
>> I have the following keybinding that work with previous versions of
>> XFree86:
>>
>> Key Left A C CursorMove -1 +0
>> Key Right A C CursorMove +1 +0
>> Key Up A C CursorMove +0 -1
>> Key Down A C CursorMove +0 +1
>> Key Left A SC CursorMove -10 +00
>> Key Right A SC CursorMove +10 +00
>> Key Up A SC CursorMove +00 -10
>> Key Down A SC CursorMove +00 +10
>>
>> When i upgraded to XFree86 4.0, and enabled 2 heads, using Xinerama, I have
>> one giant resolution and nothing knows differently:
>>
>> xdpyinfo results:
>>
>> default screen number: 0
>> number of screens: 1
>>
>> screen #0:
>> dimensions: 3200x1200 pixels (1084x406 millimeters)
>> ...
>>
>> anyways, the problem is that if the cursor is on my primary monitor,
>> everything works fine, but if I'm on the secondary monitor, then the
>> control+arrows stop working. no response at all. All other fvwm keys seem
>> to work just fine, just control+arrows stop (or so I've noticed).
>>
>> Now, its not that fvwm isnt getting the keys, since when i hit
>> control+arrows, my xterm temporarily looses focus, just like normal (the
>> cursor becomes hollow until i let go of the arrow key).
>
>That doesn't mean that fvwm gets the events. It only indicates
>that the application noticed something.

how can i see if fvwm is getting the events?

>If Xinerama is really what I think (a large root window;
>applications are unable to tell the difference between
>one big and many small monitors), this looks lika a bug
>in the Xinerama code.

Yah, one large root window. so thats what I was thinking, but I can't
possibly see how Xinerama has anything to do with this.

xev is still getting the same events. I wrote a program to wrap the pointer
around and it works just fine on the second monitor. The control key works
in applications, the rest of the fvwm key bindings still function.

I'd like to pinpoint the problem here, and either get it fixed in FVWM or
Xinerama. You know fvwm code inside out, so I figured you would be able to
help me with ideas on making sure the bug is not in FVWM. Then I can go
talk to XFree people.

-- 
___________________________________________________________________________
Danny Dulai                                           Feet. Pumice. Lotion.
http://www.ishiboo.com/~nirva/                            nirva_at_ishiboo.com
--
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 Thu Mar 16 2000 - 01:37:55 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:50 BST