I'm trying to strengthen the docs on shortcut specifications,
and am finding there's contradicting behavior with casing of
the keyboard codes. (There's already an STR about this)
What is the /intended/ behavior for shortcuts like:
'a' -- Should only lowercase 'a' trigger shortcut? Or both 'a'
and 'A'?
'A' -- Should this imply Shift-A, or just 'a' too?
FL_CTRL+'a' -- Should only allow Ctrl-A, and not Shift-Ctrl-A?
FL_CTRL+'A' -- Should this imply Ctrl-Shift-A? Or only Ctrl-A?
As a test, I found on linux:
'a' as a shortcut works for BOTH lower and uppercase 'a'. (probably is WRONG
to me)
'A' as a shortcut only works for Shift-A (ie. FL_SHIFT is implied, seems
RIGHT to me)
FL_CTRL+'a' only works for lowercase 'a', not uppercase (seems RIGHT to me)
FL_CTRL+'A' only works for Ctrl-Shift-A (ie. FL_SHIFT is implied, seems
RIGHT to me)
I suppose anything is right, as long as treatment is 'consistent' for all the
above,
and across platforms. (I'm pretty sure currently the above behavior is not
consistent
across platforms)
What I'd like to do is document the /intended/ behavior, so that bugs can be
properly reported for contradicting behavior, or if unfixable, at least document
the current platform specific behaviors.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
