> On 17.03.2011 12:26, Albrecht Schlosser wrote:
>
> > I have no idea why my patch changed the behavior of take_focus()
> > in such a way, but I'll investigate this later - I'm really
> > curious. If anybody could tell me, I'd appreciate it...
>
> For the record: it turned out that something else changed the
> take_focus() behavior. This seems like a regression in fltk 1.3
> and should be investigated.
I found the regression: it's in svn r7788, file FL/Fl_Widget.H:
Index: FL/Fl_Widget.H
===================================================================
--- FL/Fl_Widget.H (revision 7787)
+++ FL/Fl_Widget.H (revision 7788)
@@ -752,7 +752,9 @@
&& visible()) but is faster.
\retval 0 if the widget takes no events
*/
- unsigned int takesevents() const {return
!(flags_&(INACTIVE|INVISIBLE|OUTPUT));}
+ unsigned int takesevents() const {
+ return !output() && active_r() && visible_r();
+ }
/**
Checks if the widget value changed since the last callback.
===================================================================
This was done for STR #2420. The log says:
"Fixed tab key navigation to inactive widgets (STR #2420),..."
This needs to be investigated further, maybe we must reopen the STR.
_______________________________________________
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
