You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following settings works together, however they are labelled in 2 different sections.
Do we want to harmonize them under a common setting category ?
ayon+settings://core/publish/CollectAnatomyInstanceData/follow_workfile_version: global enable/disable follow workfile feature
ayon+settings://core/publish/CollectSceneVersion/hosts: host list of which host(s) collect scene version
How would you imagine the implementation of the feature?
We could rename one or the other so they fall back under the same category:
robin-ynput
changed the title
Harmonize CollectSceneVersion/hosts and CollectAnatomyInstanceData/follow_workfile_version
Harmonize CollectSceneVersion/hosts and CollectAnatomyInstanceData/follow_workfile_version settings
Feb 3, 2025
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
This follows a discussion from #1111 (comment)
The following settings works together, however they are labelled in 2 different sections.
Do we want to harmonize them under a common setting category ?
ayon+settings://core/publish/CollectAnatomyInstanceData/follow_workfile_version
: global enable/disable follow workfile featureayon+settings://core/publish/CollectSceneVersion/hosts
: host list of which host(s) collect scene versionHow would you imagine the implementation of the feature?
We could rename one or the other so they fall back under the same category:
ayon+settings://core/publish/CollectAnatomyInstanceData/follow_workfile_version
ayon+settings://core/publish/CollectAnatomyInstanceData/hosts
or
ayon+settings://core/publish/CollectSceneVersion/follow_workfile_version
ayon+settings://core/publish/CollectSceneVersion/hosts
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: