> I don't need an example, I subclassed Window and added members to > point to Widgets the first time I did something like this. Both > methods seem to be a bit high in maintenance overhead though. I > was just hoping there was a 'name' field or something similar > already in place to identify the Widget. > > Just for clarity's sake, most of you are assuming that this is > being done in one of the callbacks. This is being done to update > the state of the GUI due to changes outside the GUI.
The same principle applies. In your class you can either make the widget members public and access them from wherever you need in your own code, or better yet, use member functions to update them. The advantage of the second is that you can create an abstract class to define the interface, and use this in the code, so that you can decouple the business logic and the user interface. > Also, I'm the only (=20) person using flkt2 ;) I think there are several people *using* fltk2, *and* lurking here, but nobody apparently doing active development. Volunteers welcome :-) D. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
