Author: greg.ercolano
Date: 2013-01-04 00:15:12 -0800 (Fri, 04 Jan 2013)
New Revision: 9784
Log:
Added Fl::run() to list of things not to call in child thread..
Modified:
branches/branch-1.3/documentation/src/advanced.dox
Modified: branches/branch-1.3/documentation/src/advanced.dox
Devs: shouldn't we add Fl::run() to that short list?
I'd vote yes, though we probably need someone who really understands that
code (Matthias?) to pitch in with an opinion...
Yes, absolutely. Fl::run() is basically: for(;;) { Fl::wait(); }
Done, r9784.
On 04.01.2013 03:12, Denton Thomas wrote:
Albrecht wrote:
It's not perfect, and maybe some of the changes would turn out
to be useless... just take it as a base for more own experiments.
Thanks for all this, Albrecht. I'll certainly use those immediately. I
appreciate it, as this is part
On 04.01.2013 10:05, Albrecht Schlosser wrote:
the scroll widget (see the notes and the callback). You may
need to call the parent's redraw method as well, if you have
a frame box time somewhere, so that the redraw doesn't draw
... frame box TYPE ...
(fingers faster than mind ;-) )
Albrecht
Albrecht wrote:
Oh, yes, that's certainly true. If navigation happens to
succeed in a subgroup, then this subgroup does it all. No
parent group will notice. You could maybe derive an own
Fl_Group class to do this in conjunction with its parent
YourScroll class, but this could be a never
On 04.01.2013 12:36, Denton Thomas wrote:
Albrecht wrote:
Oh, yes, that's certainly true. If navigation happens to
succeed in a subgroup, then this subgroup does it all. No
parent group will notice. You could maybe derive an own
Fl_Group class to do this in conjunction with its parent
All,
I'd like to know if there are more FLTK users who have the need
to track the widget that currently has the focus. If this was a
common problem, we could probably add something to FLTK to make
this easier. It's not easy with current FLTK methods, as can be
seen in the current discussion with
On 04.01.2013 12:36, Denton Thomas wrote:
New handle() below. I like this version a bit better, if only because it
meets your original suggestion for a simple solution.
Please see also my RFC in fltk.general:
http://www.fltk.org/newsgroups.php?gfltk.general+v:35878
Albrecht
8 matches
Mail list logo