One other thing. I really like how with the "Client Review" system you can "prepare" a review, and maintain it, adding and removing clips, etc. Is there any plan to have a similar functionality with the new player?
Reading this example action:
There are many example actions in the Ftrack documentation with varying structures, but this is the only one that I've seen that sets the action identifier with an uuid, making the identifier unique to each action instance, which is helpful in avoiding crosstalk between users using the same Ftrack-connect plugins.
Another example like this uses an internal register function inside the class to filter the action by user.
Which of these methods would be considered best practice to safely configure a client-side action?
All platforms: Download 1.0.3
Changes since last version
fixed : Action icons not correctly loading.
changed: Version comments are published as Perforce changelist description.
new : Update docs to include timeout solution for credentials.
How to install
remove previous nuke studio plugin from : <ftrack-connect-package>/resource/connect-standard-plugins/
download and uncompress the new version in :<ftrack-connect-package>/resource/connect-standard-plugins/