> I probably stated it poorly - you are correct, but the > problem I have is > callbacks are only called for one value change, not both. > Thus, ALL my > radio button callbacks have to check all the other buttons to > find which > one got turned OFF and deal with it in order for the app to remain in > sync with the gui, which isn't something I want to keep track of - it > makes a royal pain in the butt to separate presentation from > calculation. What I was hoping for was the button going OFF > would also > be called; then, for example, if one valve is opened, the previously > open value would get closed without the opening value having to worry > about that case. Maybe a RADIO_ACTIVE type in addition to RADIO?
Yes, get it. What I often do is assign all the buttons in a radio group the same callback, and then, in the callback, identify which button triggered the cb, update the others accordingly and do the actions... Not ideal maybe, but I think it gets you to where you want to go? -- Ian SELEX Sensors and Airborne Systems Limited 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
