On Mon, 2003-08-04 at 09:10, Egbert Eich wrote:
> Bugzilla 558 requests to change the behavoir of shift+<numpad arrow keys>
>
> > In reasonable X GUIs (GNome/KDE), shift + <regular arrow key> selects text.
> > But if i press shift + <numpad arrow key>, i get numbers! So the current XKB
> > behavior makes Shift kind of like the "lockless" version of Numlock, which is
> > insane, IMHO. the numpad keys are *arrow* keys (unless numlock is turned on)
> > by definition. Shift should have no effect on them. The current behavior is
> > contrary to what Windows users are used to (and highly annoying for this
> > reason). I see no reason to have a different behaviour to Microsoft in this
> > regard (seeing as though this can potentially piss off 90+% of users), apart
> > from the sake of wanting to be different (which is not a good reason).
> > Instead of a being just a whinger, I provide this patch (please apply with -l)
>
> This requests sounds reasonable so I would like to find out if
> somebody has a strong opinion on this issue.
> If not I will commit the supplied fix.
Well, the current setup is compatible with the non-XKB behavior
documented in section 12.7 of the Xlib reference manual.
So, there are some compatibility concerns about changing it.
You could imagine an application that documented shortcuts
with respect to the current system.
I don't think that is necessarily a killer objection if there
are significant usability advantages to a different mapping,
but what seems to be missing above (and in the bug report) is more
details of *why* this behavior is annoying.
While it may be unexpected, it doesn't seem to me that pressing
<shift>+KP_whatever is something you would do by accident.
And I wouldn't expect many people to have learned to use
<shift>+kp_arrows for extending the selection.
Regards,
Owen
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
