Duncan Gibson wrote:
>> OK - here's a version of the code for determing the "true" app path...
>
> Might be an idea to submit this as a HOWTO or FAQ article, no?
Or, I hesitate to recommend, perhaps in a separate support library
eg. fltk_os.lib which could have non-gui, OS specific support stuff.
I think our own test tools might be able to make use of this,
for instance on the Mac, accessing the dir the program was invoked
from to be able to access the this.app/Contents/* directory in order
to load default preferences, icons, etc.
I can think of a few things that are frequently asked on the newsgroup
that could perhaps fit into a general 'os' category.
To avoid the slippery slope of ending recreating an entire OS
portability layer, perhaps we could limit ourselves to OS calls
only in support of FAQs related to the support of GUI programming,
such as to aid in locating preferences..
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
