Please describe the feature you have in mind and explain what the current shortcomings are?
Current implementation of shim on MacOs does not allow to be used as path for automation that can wait for executed process to end. The reason is related to custom scheme handling.
How would you imagine the implementation of the feature?
We could add 2 executables to the ship app. One whic is used as "main" executable of .app bundle that would work as current ayon executable, and second which would be the real ayon executable which is triggered from the main executable.
In that case /Applications.app/Contents/MacOs/ayon could be used for automations.
Please describe the feature you have in mind and explain what the current shortcomings are?
Current implementation of shim on MacOs does not allow to be used as path for automation that can wait for executed process to end. The reason is related to custom scheme handling.
How would you imagine the implementation of the feature?
We could add 2 executables to the ship app. One whic is used as "main" executable of .app bundle that would work as current ayon executable, and second which would be the real ayon executable which is triggered from the main executable.
In that case
/Applications.app/Contents/MacOs/ayoncould be used for automations.