> Everything worked perfectly, no issues, then i added a help > window, rebuilt and suddenly, on callback, my start button > label (which switches between start/stop/continue) was > 'overwritten', not refreshed correctly so that the previous > label was still visible underneath also, like the label had > been redrawn but the button face had not. > It turned out nothing to do with additional window but that i > had also messed around with different frames and boxes for > the button, when it was set to a different frame the problem occured. > > I reset to a 'default' mask, same as the other buttons and > the problem stopped. > Would this be system specific? And if so can i expect > portability issues even with 'safer' default buttons on other systems?
The "frame" types are just that, they only redraw the frame of the widget, not the widget's "face" at all. So, you generally *never* want to use a "frame" type, except for a widget where you plan on doing *all* the redrawing explicitly yourself, e.g. in a subclasses draw() method. And even then, the "box" types are often more appropriate than "frame" types. In general, unless you *know for certain* that you need to use a "frame" type, you should use a "box" type. 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
