I imagine the solution would be an option in the fluid properties that would let one select 'dynamic' vs. 'static' population of the widget.
I'd suggest making an RFE STR for fluid, and if possible, refer to the patch you mentioned. It would certainly be handy, as I myself prefer dynamic creation of menus to static. On 11/30/11 10:44, Domingo Alvarez Duarte wrote: > It's a good idea for a few items, I like it although the main problem will > remain unchanged, thanks ! > > On Wed, 30 Nov 2011 18:08:14 +0100, Greg Ercolano <[email protected]> wrote: > >> On 11/30/11 03:01, Domingo Alvarez Duarte wrote: >>> I already pointed this some time ago and I was pointed to a aptch that >>> generates static class entries instead of global ones, but today I was >>> trying to use fluid to add a FL_Choice to a class and found that it also >>> generates global static entries instead of class entries. >>> >>> Have someone else solved this ? >> >> My approach is to just leave the menu empty inside fluid, >> and use the 'extra code' to populate the menu using add() _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
