On Thu, 10 Aug 2000, steve rieger wrote:
> thank you,
> the num lock was on
>
> can you please explain the relationship between those
Num lock, like shift, ctrl and meta [alt] is generally treated as a
modifier by X. There are 3 things that influence what occurs when you
get a keypress/mouse click:
Context [where am I: window, titlebar, root-window, etc]
Modifier [shift, alt, ctrl, meta, num lock]
Key [The actual key our mouse button pressed]
The modifier control has machanisms to say
"no modifiers" => N
"any modifier" => A
"Shift+Ctrl" => SC [I think]
or you can specify the combination of modifers, but it's hard to exclude a
specific modifier: you just have to specify the same reponse for all
possible sets of modifers you want to apply. I think the lates betas can
ignore specific modifiers, but I think this is an across the board thing,
not a per action thing. You can also use xmodmap to attach modifiers to
keys:
The following, placed in a file and read with xmodmap -file <file>
keycode 115 = Super_L
keycode 116 = Super_R
clear Mod4
add Mod4 = Super_L
add Mod4 = Super_R
makes the melted-window keys into 'Super' keys, and then maps the Super
keyboard modifer onto 'Mod4': I can then use
Key KP_Left A 4 Scroll -100 +0
in my .fvwm2rc [for example] to make [Melted Window] + [Keypad Left] move
me one page to the left in X.
Num lock is usually mapped to Mod2, so Clear Mod2 would probably solve
your numlock proplem.
--
Q: Why did the tachyon cross the road?
A: Because it was on the other side.
--
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 Fri Aug 11 2000 - 07:05:58 BST