On 04/12/12 13:54, Domingo Alvarez Duarte wrote:
> And I'm testing Flu_Browser_Tree and it only draws (call draw) on nodes
> that are visible on the viewport.
Yes, sounds like they have that optimization is in that
widget already, which might be useful for reference.
I think I mentioned already: the Fl_Tree::draw() code needs
some optimization for the special case of when FLTK widgets
are used in the tree (instead of just the regular text items).
The point in the code that I think would address this
is to replace the call to Fl_Group::draw_children()
with something that first checks if the xywh extent
of each child widget is inside the viewport before calling
that widget's draw() method.
I know and understand what you're requesting regarding
the optimization; it just hasn't been done yet.
Feel free to submit a patch, or wait for one of us to
make the optimization.
If you have a small example program that demonstrates
the problem you're facing, do include it with the STR
so we can be sure the problem you're seeing gets solved.
_______________________________________________
fltk-bugs mailing list
fltk-bugs@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-bugs
