> > > Yes, it both sounds great to me. I suggest an additional > function, maybe > > > > const char *fl_application_path(); > > > > Which would return a pointer to a buffer that needs to be > free'd (since we > > need this path usually only once). And I love the idea of > adding a new enum > > member!
All, are we thinking of this for 1.3.0 or do we need to punt this further down the line? It doesn't look like an ABI breaker - but I am not sure about whether changing the enum is an issue or not. In either case, does somebody (maybe Nicholas?) need to raise an STR just to remind us all? 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
