Quoting Ivan Pascal <[EMAIL PROTECTED]>: > > % setxkbmap -model pc104 -layout us_intl > > or > > % setxkbmap -model abnt2 -layout br > > => Scroll_Lock leds works > > They are 'old layouts'. > > > % setxkbmap -model pc104 -layout us > > or > > % setxkbmap -model pc104 -layout pt > > => Scroll_Lock leds dont work > > They are new ones.
> The thing is new layouts have three-four levels and need a modifier > bit > for switching to those levels. But all real modifiers are already > used: > Lock, Shift, Control - according their names, and unnamed ones > (Mod1-Mod5) > are Alt, Meta, NumLock, ScrollLock and one for a Mode_Switch emulation > for > compatibility with the core protocol. > Thus for the new ThirdLevel modifier I had to sacrifice one of them. > The ScrollLock modifier seems me most unused and now this bit is used as > the > ThirdLevel modifier (of course the ScrollLock key still prodice a > corresponded > keysym). But the ScrollLock indicator still configured to show state > of > modifier bound to the ScrollLock keysym. > I think if complaints will come I'll make an option that maps the > ScrollLock > virtual modifier to some real one. Otherwise we can use the indicator > for > something else. I think there won't be too many complaints about the ScrollLock leds not working. I am just not sure if there aren't programs that rely on ScrollLock working as before. For safety, I believe a xkb option for that case would be a good idea. BTW, I just tested the changes for MouseKeys, it is now working properly, thanks Ivan. > -- > Ivan U. Pascal | e-mail: [EMAIL PROTECTED] > Administrator of | Tomsk State University > University Network | Tomsk, Russia Paulo _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
