Please describe the feature you have in mind and explain what the current shortcomings are?
With flame, users might often open the software in a "global" context and then work on different shots. For example they might launch the application from /shots/timeline and then work on /shots/seqA/a010 , /shots/seqB/b042 etc) This means if a user opens the creator ui, it will default to the "global" context.
Overwrite that, so it defaults to the context of the current batch file (if it has been published before), or fallback and attempt to auto detect the context from eg.: read nodes within the current batch.
Additional context:
_This issue was automatically created from AYON ticket YN-0859
Please describe the feature you have in mind and explain what the current shortcomings are?
With flame, users might often open the software in a "global" context and then work on different shots. For example they might launch the application from /shots/timeline and then work on /shots/seqA/a010 , /shots/seqB/b042 etc) This means if a user opens the creator ui, it will default to the "global" context.
Overwrite that, so it defaults to the context of the current batch file (if it has been published before), or fallback and attempt to auto detect the context from eg.: read nodes within the current batch.
Additional context:
_This issue was automatically created from AYON ticket YN-0859