On 26 Oct 2007, at 19:10, Greg Ercolano wrote: > BTW, check that your app still has resource forks assigned to it > with ls(1), e.g. > > ls -la yourapp/..namedfork/rsrc > > ..does the 'size' field show a non-zero value for your app? > If zero, the app lost its resource forks.
I don't have access to any 10.5 boxes yet, but I think I remember reading on one of the Apple lists that that style of resource fork is on it's way out. Certainly I have seen some discussion of API changes in 10.5 that make accessing the res fork from *within* the app fail, for some of the existing res fork methods (of which there are many). Other techniques are reputed still to work. What that means to us right now is not clear to me! However... I did think that at one point we had modified the fltk OSX port to use other methods to make the app foreground if it was started on 10.4 without a res fork. It is possible that the method used no longer works, or perhaps checks for 10.4 explicitly, or something. It's a while since I looked at any of this... and I'm not sure I understood it even then. Bundles should work without a res fork, however, so that may be the solution. It is a pain if you also want an app that is easily invoked from the command line, though. -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
