DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2479 Version: 1.3-current Fix Version: 1.3-current (r8067) Thanks Albrecht! Yes, the cross platform research was what took most of the time. Responding to your items: (1) Feel free to correct any docs you think are unclear. I think I maintained the previous doc terminology which seemed consistent to me, maybe I'm missing something. (2) It's supposed to be intentional, but I'm not 100% sure of these rules myself. When in doubt I tried to maintain previous behavior. My main goal was at least to document the intention of the return value (hence the consistent use of 'ignore/pass up' vs 'ignore/absorb'). The only relevant info I could find is the OSX HIG indicates certain keystrokes are 'reserved for the OS' and should therefore not be handled by apps, eg: "Reserved Keyboard Shortcuts" on this page: http://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGUserInput/XHIGUserInput.html#//apple_ref/doc/uid/TP30000361-TP9 When in doubt, I tried to maintain the previous behavior. I made sure at least the comments reflected the behavior ('ignore/pass to parent' vs 'absorb and ignore'). Didn't cite reasons for it though, as I wasn't sure myself. These return values should probably be checked over. I think mainly the idea is when the input field has focus, certain events should be passed up that might affect eg. scrollbars or shortcuts and thus return 0, whereas others should only stay within the widget so as not to possibly affect parent widgets. (3) Ah, good catch. I actually caught one or two of those myself while doing the code, and made a note to check for others, but forgot to follow up on a check of all of them. Will fix. Link: http://www.fltk.org/str.php?L2479 Version: 1.3-current Fix Version: 1.3-current (r8067) _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
