> Fl_Value_Input *x = (Fl_Value_Input *) button->parent()->child(2); > Fl_Value_Input *y = (Fl_Value_Input *) button->parent()->child(3); > Fl_Value_Output *z = (Fl_Value_Output *) button->parent()->child(4);
I would generally caution against this as a way of accessing other widgets - it is error prone and hard to maintain. A simple reorganisation of your UI could easily throw all your assumptions about widget order, breaking your code. Indeed, as others have already pointed out, it is probably the ordering of the child widgets that is causing your problem. There are simpler, and more easily maintained, ways of referencing other widgets, so I recommend you look into those instead. 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
