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).
xev dumps of when I hit control+left arrow once and let go:
Primary montior:
KeyPress event, serial 25, synthetic NO, window 0x2a00001,
root 0x2a, subw 0x0, time 3998046814, (94,181), root:(1391,739),
state 0x0, keycode 66 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 characters: ""
FocusOut event, serial 25, synthetic NO, window 0x2a00001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 25, synthetic NO, window 0x2a00001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 25, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 25, synthetic NO, window 0x2a00001,
root 0x2a, subw 0x0, time 3998051556, (126,181), root:(1423,739),
state 0x4, keycode 66 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 characters: ""
------------
Secondary montior:
KeyPress event, serial 25, synthetic NO, window 0x2a00001,
root 0x2a, subw 0x0, time 3998110546, (363,129), root:(1660,687),
state 0x0, keycode 66 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 characters: ""
FocusOut event, serial 25, synthetic NO, window 0x2a00001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 25, synthetic NO, window 0x2a00001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 25, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 25, synthetic NO, window 0x2a00001,
root 0x2a, subw 0x0, time 3998114459, (363,129), root:(1660,687),
state 0x4, keycode 66 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 characters: ""
Everything is the same, except timestamps and the coordinates that the
keypresses happened at. Each monitor is running 1600x1200, so if you notice the
X position of the secondary montior event is 1660.
Any ideas on getting this key to work?
--
___________________________________________________________________________
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 Wed Mar 15 2000 - 23:55:11 GMT