> I'm proposing to add a second changed flag to Fl_Widget, this > second one > will not be reseted after a callback like the actual one is. > > I'm working with windows with several Fl_Inputs and some of > then uses > callback to allow calculations when the value changes, but at > the end I > need to know which ones have changed over the session and > because the > CHANGED flag is cleared after the callbacks this information is lost. > > With a second flag that is not reset by the callback I can > easily get the > changes over the section. > > I think that this can be util for more people and for FLTK as > well, so I > propose to add to the official distribution, this change is > transparent > for applications that do not use it explicitly, so all code > made till now > should work as before.
I think, if it were me, I'd just derive my own widget to add that functionality, rather than changing the core lib. Oh, I see Mike suggests using the user_data instead - yes, that seems like a good way to go. Maybe use that to point to a struct that holds interesting details fo whether the widget is dirty or not, and which group it belongs to and so forth... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
