From: Jack J. <ja...@or...> - 2002-02-04 11:26:24
|
On Saturday, February 2, 2002, at 07:03 , Jim Ingham wrote: > I haven't figured out a good workaround for this yet, but you have to > have > the app in an App bundle with the appropriate support files for it to > launch > properly. There is some other way to invoke the proper voodoo - I have > seen > an app or two that do, but I don't know what it is. For some reason (i.e. I haven't the foggiest idea what I did:-) running from the command line works fine for Python.app. But: it could well be that I've always tried it by giving a full path to run it, so maybe that's a difference? My feeling is that the whole "magic" for turning a unix process into a MacOSX "application process" is contained within the process itself, i.e. it looks around in the filesystem in the area surrounding the executable and if it looks sufficiently .app-bundle-like it will do the right thing. So you may want to look at what's in your bundle and compare it to what is in the Python.app bundle, or in bundles of other programs that do the right thing when run from the command line. Another difference (but your no doubt aware of this) is of course that you won't get the initial AppleEvent and that you don't get the funny argv argument that the finder (or someone else) gives you when double-clicking the .app. -- - Jack Jansen <Jac...@or...> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - |