> Ah, I was wondering about that. The first "show()" call in an > application always should be "show(int,char**)" for this and other > reasons. I beleive it is in the docs somewhere, but I can see > how easy > it is to get that wrong.
I have a chunk of code where (due to the stupid and awkward args processing I'm doing at application startup) it isn't practical to call show(argc, argv)... So I call show() instead, but always make a point of calling Fl::get_system_colors() before I call show() the first time. I haven't looked closely at the fluid sources, but maybe there's some reason there why it doesn't call show(argc,argv). Anyway, what I was going to suggest is that Fl::get_system_colors() could maybe be extended to cover setting the xclass, to cover those cases where show() is called "wrongly" at initialisation. Would that help at all? > (plus argv[0] is not always valid anyways, but IIRC Greg has a > collection of functions to get the executable path on all platforms?!) That might have been me, actually. Or at least, I have code for determining the executable path on the majority of platforms, if we need it. -- 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-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
