Greg Ercolano wrote: > > I suppose an easy way to bring sanity/consistency would be to make an > edict > that the case of the letter code will be ignored (downcased) so that > 'A' or 'a' don't affect casing, and the only way to get a shift key > is to include the FL_SHIFT modifier. (eg. AND off the modifier bits, > do a tolower() on the resulting value, then OR the modifiers back in)
This sounds sensible to me... > Then it would just be a matter of making sure the downcased codes all > work as expected, and documenting the behavior. > > This would at least remove the potential for odd behavior for 'a' vs 'A', > and I think would be a 'clear' rule to remember. > > I guess it needs to be determined, though, if casing of alpha characters > should matter. I think it does - quite a few applications I have used (on various platforms, and not written by me) do different actions for CTRL-SHIFT-<char> than they do for CTRL-<char>, so it must be that the SHIFT state is being detected as you suggest. -- Ian _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
