> I don't like the idea to modify the FL_ALT state in the menu code. Indeed, nor do I really, in particular since it depends on Fl::e_state being public, which might not always be the case...
> I can contribute an idea and a little statistic: We could easily > extend int Fl_Widget::test_shortcut(const char *t) (the function in > question WRT STR #2199) to accept another argument, something like > "int require_alt" as a boolean decision. Yes - this was an idea I had too, but I was worried about breaking the API so I backed away from that. I guess if we provided a wrapper function with the old API that always called the "new" version with the "require_alt" hard coded appropriately, then that could be OK - most callers would not even know anything had changed... > This could be used depending > on the context of the caller. And here comes the statistical part: > grep shows 26 hits in FL/* and src/*.c* for _any_ form of the string > "test_shortcut". Some of these are comments, others are calling > different test_shortcut methods... Maybe that helps? Just my 2 ct. Indeed - and most of those probably would not need to change, as they would still call as before, so... The trick is that I still don't know which particular calling context needs to get this "right". And of course, this is all WIN32 specific, so we need to *not* change the behaviour for the other platforms, too. SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
