| |
| |
On 9/2/21 10:49 AM, Albrecht Schlosser
wrote:
I do. It's really strange.
I've been looking at this too, and it seems to me there's some
strange
behavior in the Fl_Tabs::value(Fl_Widget*) method, where somehow
during
the loop, the last widget is somehow becoming visible() before
it's set visible.
Haven't come to conclusions yet, but it sure seems in
Fl_Tabs::value(Fl_Widget*)
during the loop, calling hide() on the first child (Tab A)
causes the /last/ child (Tab C)
to suddenly become visible() for some reason, causing confusion
in the loop.
I'm suspecting the Fl_Group::handle() method code for
FL_SHOW/FL_HIDE events
to be the "culprit".
I have to run away mid-debug, but that's where I left off.
Anyone wanting to dig deeper, I suggest use the above to get
past that
first level of obfuscation, as that's a weird trip down the
usual event rabbit hole.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/3535c198-647a-5443-a22b-f1c127ecef99%40seriss.com.
[ Direct Link to Message ] | |
|
| |
