Started by John Hagan, September 14, 2020, 02:07:03 am
Quote from: John Hagan on September 15, 2020, 12:33:12 amI understand that the Finder doesn't pass the file to open as an argument to the app via the old argv interface,
Quote from: John Hagan on September 15, 2020, 12:33:12 ambut the MacOS framework does provide a mechanism for the Finder to send a message to an app it launches with the reference to the selected file that caused the launch. That's how every other MacOS app gets the file to open when invoked by the Finder.
Quote from: John Hagan on September 15, 2020, 12:33:12 amI think it's just a few lines of code to implement the handler for the message.
Quote from: John Hagan on September 15, 2020, 12:33:12 amNow that I'm working on a Mac instead of Windows, I was thrilled to see that there is a version of Avidemux for it. However, without the ability to open files right from the Finder, my workflow is pretty badly impacted. And, even in its current form where it can be configured to launch another instance based on a file type (but not load it) from the Finder, I do it because it's the only way I can get more than one instance to run at the same time.
Quote from: undefinedI hope you will consider adding the Finder open file capability. It would allow Avidemux to serve as a full fledged Mac app suitable for associating with video file types and launching with the Finder.
Quote from: undefinedAnd, it would give me back my dearly missed multi-instance capability, too!