On 18 May 2011, at 18:29, Greg Ercolano wrote: > 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..
This might be a handy idea; if so, the two bits of code I recall posting on more than one occasion are this "app_path" code and also some code for jumping the mouse cursor to some specific location (which I refer to as "jump_cursor".) I don't think either should be in the core, but I can see that they are useful. It's a bit odd that I wrote the "jump_cursor" code though, as I'm a big fan of graphics tablets, which use absolute positioning, so the "jump" never works for me...! As an aside, it turns out the "app_path" example I posted is an old version, so the OSX bit, whilst functional, is actually a bit odd. I have a "better" version if we are serious about doing this... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
