> > > So how come it is working ok? Or is this something that has yet to be > > updated in the docs?=20 > > 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.
The program only runs from args when a file is double clicked or if the user know about such things 'dragged and dropped' onto the exe, both of which things result in argc = 2, any higher and i have fails in place, argc = 1 is ignored as i am using the GetModuleFileName (i think thats what it was called) now. The thing is aside from the error pop up, using show->(argc, argv) threw up a bug regarding file loading or memeory allocation (based on file data loaded) somwhere in the program, which i was about to trace until i found that it was due to ->show(argc,argv). i say 'due to' i mean that all my file loading and parsing is now structured without those parameters in mind directly so i will have to go and rewind the command line stuff a-g-a-i-n if i include it! either that or risk no icons i suppose. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
