-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fusion: Also update saver tool path on only task or asset change #231
Fusion: Also update saver tool path on only task or asset change #231
Conversation
Maybe I'm doing something wrong but there is no difference for me with or without this pr. |
Ok, so the reason for that is because the Also, if you were to change the templates for your project so that the subset does not include the task name then also on task change it would not change the save path to the other folder. Anyway, in short, you got 'lucky' with the fact that the task name change influences the subset name and thus would be captured as a change already in the original design. @EmberLightVFX let me know if you can confirm that behavior. |
Should be fixed with 98bed9f |
YY, I did. |
Do you get any errors in the console? Are you able to debug up to where the code triggers? Does your instance somehow not have Does it work for a newly created instance? |
…s not match current context
…github.com/BigRoy/ayon-core into enhancement/fusion_switch_asset_task_paths
Ok, so - I have implemented a change that should work for this. But admittedly, I'm not sure if I really like that having that code there. It feels cluttered and likely slow for many instances. I wonder if we have better options than this. @EmberLightVFX @iLLiCiTiT thoughts? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works.
Do we think that this would have such a massive occurrence (changing asset from current context) that it would have any noticeable impact?
I don't suspect day-to-day usage should see performance issues due to this. I'd have just preferred this to be much simpler and cleaner than this. |
Changelog Description
Also update saver tool path on only task or asset change.
Without this the path would change to the other asset/task if you combined that with a change to subset or image format but not if you only changed asset or task. Which made it quite confusing and could potentially have been overwriting files on the wrong location (not particular to that asset or task it switched to). This changes makes it way more reliable, switching asset or task will result in the new path.
Additional info
n/a
Testing notes: