> So how come it is working ok? Or is this something that has yet to be > updated in the docs?
Luck. > Or is it something that cannot be relied on > unless the show(int argc, char** argv) method is used? Yes, the later - different host OS variants behave differently. If it works for you on your box, and you only ever run it there, then no worries. It may behave differently on another box though, so best to be on the safe side... However, this generally does not happen unless you actually are passing some argument to your program at start-up. If you are not, you don't get any message popping up, so from this I infer that you are passing some arg to your app at start-up. If that is not intended,then removing the spurious arg should remove the problem. If it is intended, then I'd advocate using the Fl::args() to eat up the fltk built-in values just leaving behind the ones that you want yourself. 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
