DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2368 Version: 1.3-current Be good to see both; api option and user controlled. Matt; are you thinking as I am for user control to be command line flags parsed by show(argc,argv)? Regarding API control: it's not unusual that an app programmer is responsible for making sure certain behaviors remain consistent between releases. For instance, a programmer of input forms might take advantage of the [old] arrow key behavior for navigating their forms, or have legacy docs that document the old arrow key behavior. So I figure, FLTK could assume a default, the API could override it, and the command line flags (argc,argv) could override all the above, eg: myapp -arrowfocus=on I imagine the user needs both on and off control, so as to override whatever the app sets. And I guess we should add the docs for such flags to the existing show(argc,argv) flags. (I forget where that is) Link: http://www.fltk.org/str.php?L2368 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
