> 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?
> 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. I use nedit (quite ironic that I'm also debugging Fl_Text_Display :-) where there is a difference between some Ctrl- and Ctrl-Shift-letter handling. E.g. Ctrl-g is search again, forwards whereas Ctrl-Shift-g (or is that Ctrl-G ?) is search again, backwards. We should avoid automatic 'case folding' and should make it explicit in the documentation that 'a' is not the same as 'A' as a shortcut. But does the programmer need to test for 'A' or 'Shift-a' or both? Same goes for 'Ctrl-A' and 'Ctrl-Shift-a' I'm not a cross-platform user, so can't answer what is expected or intuitive. All we can do is be clear in the documentation and give the programmer the info to implement what they want/need. D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
