Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
Current workfiles api on host does not expect that a DCC could have opened single session for more than one project. But there are DCCs that technically do allow that (Photoshop, TVPaint, ...). It is potential danger because of project bundles. But current state is also dangerous as it is not handled at all.
How would you imagine the implementation of the feature?
I do suggest to add project_name argument to those methods that do require handle context in workfiles api, made draft PR. The argument does affect only the host integration where it can happen, it should not affect any other host at all.
NOTE: It can be by-passed even now, by first calling set current context (which does support different project), it is more things to know/handl.
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
Current workfiles api on host does not expect that a DCC could have opened single session for more than one project. But there are DCCs that technically do allow that (Photoshop, TVPaint, ...). It is potential danger because of project bundles. But current state is also dangerous as it is not handled at all.
How would you imagine the implementation of the feature?
I do suggest to add
project_nameargument to those methods that do require handle context in workfiles api, made draft PR. The argument does affect only the host integration where it can happen, it should not affect any other host at all.NOTE: It can be by-passed even now, by first calling set current context (which does support different project), it is more things to know/handl.
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response