Yes - what Greg says. For what it is worth, it is customary for me to pitch in at this point saying that for large arrays of widgets, you are far better off managing them in an array of your own making (the fltk widget management probably is not the most efficient way to handle large collections...)
Since you are using boost anyway, it should be pretty easy to manage the widget list that way, then only render (in your subclassed draw method) the ones that are actually on-screen at any given time. This is g=usually more efficient, and does not suffer from the limits on the graphical context that using the underlying flkt widget layout does... And... I see Greg has linked to a post from Matt suggesting that... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
