[STR Closed w/Resolution] Link: http://www.fltk.org/str.php?L2704 Version: 1.3.0 Fix Version: None
Thanks for the workaround. But I think to properly close this, wouldn't it be right to update the docs for add_modify_callback() to indicate this sort of thing as a caveat/gotchya, now that we've identified it? I could see others running into this, because it seems easy to think this is what the modify callback is intended for; to throw away potentially bad input. (background: I was writing a widget that derived from Fl_Text_Editor that would only allow a single line of input, but included horizontal wordwrap, and vertical scrollbars would appear if the string went off the bottom of the widget. This meant not only trapping the enter key, but ^C/^V and mouse pastes with crlf's in them. I guess handle() could trap all these things, but it gets tricky to 'prevent' pastes.. which is why I preferred to wedge my code in after the buffer was modified) Link: http://www.fltk.org/str.php?L2704 Version: 1.3.0 Fix Version: None _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
