DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2574 Version: 1.3-current The attached invisible2.patch fixes this bug, as confirmed by the OP. The issue is that, whereas the doc says that if flag INVISIBLE is on, a widget can be invisible but can receive events, the Fl_Widget::takesevents() function does not allow this behavior. The fix, in essence, would be: - add set_flag(INACTIVE) in Fl_Widget::hide() - add clear_flag(INACTIVE) in Fl_Widget::show() - remove from Fl_Widget::takesevents() the requirement that visible_r() be true. An invisible, event-receiving widget is thus obtained by: mywidget->hide(); mywidget->activate(); The simple call mywidget->hide(); creates, as always, an invisible, eventless widget. Is this fix OK? Or, does anyone sees undesirable side effects ? I'm unsure whether to commit it at this point. This may just wait after the 1.3 release. Link: http://www.fltk.org/str.php?L2574 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
