[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2027
Version: 1.3-current
Fix Version: 1.3.0 (r6576)
Fixed in Subversion repository.
Link: http://www.fltk.org/str.php?L2027
Version: 1.3-current
Fix Version: 1.3.0 (r6576)
___
fltk-bugs
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
This is just a reminder for who will have some time to finish 2026 (which
btw hides quite some anomalies more serious than the bug report on the
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
I think I'm going with this hotfix for now (leaving the FL_UNFOCUS
fallthrough):
case FL_HIDE:
fl_reset_spot();
if (!readonly() &&
-
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
Not sure what to offer without making a new bitflag.
I noticed some other bad behavior with the current release as well:
the callback is trigger