Peculiar observations of (the CommandLine) property on OSX

[WrongPillNeo webforumsuser@macromedia.com]

Hi all,

I wrote a little application that reads and writes its own file type. I wanted to launch the projector when i double clicked on this file on my desktop.

In windows i associated that file-type extension with my projector.exe and on the mac i created a new file type and associated projector.app with that file type.

In windows the commandline argument was recieved when the file was double clicked on from the desktop..the file opened successfully with the lingo code in my pojector.

On the mac OSX ( i didnt try it o OS9) i was not expectiing it to work....since the several documentations say that the command line is not supported on MacOS...This was the case. ....i.e it did not work..

what is interesting is when i put the projector Icon in the Dock (taskbar similar to windows), the command line was read (i.e the path name of the file) and the file opened with my lingo code successfully


Any help/feedback about this will be most welcome since i would want to make this more consistent...

thanks

PV

[Unregistered]

what is interesting is when i put the projector Icon in the Dock (taskbar similar to windows), the command line was read (i.e the path name of the file) and the file opened with my lingo code successfully

Hi PV.
Thanks for posting about this. I'm working on something similiar using D11.5 on Mac and found no joy with the CommandLine. But I'll try your method of having the projector icon in the Dock.

Did that launch the file and app. even when the app was not already running?

Also, did you do anything special to associate your file extension with your projector app?

I have a creator code for my app, but I don't see how the OS makes the association between that and my data files.

Thanks,
Tom B.