DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2094 Version: 1.3-current Seems the problem is right after an FL_UNFOCUS comes to the widget. I'm thinkin the problem might be an unintended fallthrough in the case statement for FL_UNFOCUS in Fl_Input_::handletext() (see <-- marker): ---- snip case FL_UNFOCUS: if (active_r() && window()) window()->cursor(FL_CURSOR_DEFAULT); if (mark_ == position_) { if (!(damage()&FL_DAMAGE_EXPOSE)) {minimal_update(position_); erase_cursor_only = 1;} } else //if (Fl::selection_owner() != this) minimal_update(mark_, position_); // <-- UNINTENTIONAL FALLTHRU? case FL_HIDE: fl_reset_spot(); if (!readonly() && (when() & (FL_WHEN_RELEASE | FL_WHEN_NOT_CHANGED))) maybe_do_callback(); return 1; ---- snip I think FL_UNFOCUS is falling through, to FL_HIDE's maybe_do_callback(). Link: http://www.fltk.org/str.php?L2094 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
