Re: [fltk.bugs] [MOD] STR #2795: Fl_Tree: needs to be optimizedtohandlevery large contents (>10000)

2012-04-12 Thread Domingo Alvarez Duarte
And I'm testing Flu_Browser_Tree and it only draws (call draw) on nodes that are visible on the viewport. ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs

Re: [fltk.bugs] [MOD] STR #2795: Fl_Tree: needs to be optimizedtohandlevery large contents (>10000)

2012-04-12 Thread Domingo Alvarez Duarte
For comparison sizeof(Flu_Tree_Browser) = 92 , sizeof(Flu_Tree_Browser::Node) = 92 and they have a lot of functionality and facilities to query tree nodes. ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-b

Re: [fltk.bugs] [MOD] STR #2795: Fl_Tree: needs to be optimizedtohandlevery large contents (>10000)

2012-04-12 Thread Greg Ercolano
On 04/12/12 12:02, Greg Ercolano wrote: > Fl_Tree > | > |--> Fl_Tree_Item -> Fl_Button > |--> Fl_Tree_Item -> Fl_Button > |--> Fl_Tree_Item -> Fl_Button > > ..whereas if Fl_Tree_Item derived from Fl_Widget, then you > could probably create something more memory frugal, such as: