Scene saved validator about pyblish-magenta HOT 5 CLOSED

This was included in one of the earlier commits.

The two relevant plug-ins at the time were:
https://github.com/pyblish/pyblish-magenta/blob/ba658c67cc4b6cc684f98db89bfba4b54699f3aa/pyblish_magenta/plugins/_validate_scene_saved.py
https://github.com/pyblish/pyblish-magenta/blob/ba658c67cc4b6cc684f98db89bfba4b54699f3aa/pyblish_magenta/plugins/collect_scene_modified.py

Note that I disabled it back then because it was annoying that some of the Collectors or method calls would make Maya assume the scene was modified even if only queried for content. For example, does cmds.file(exportSelected=True, preview=True) trigger a scene modified? There are likely many commands that trigger it.

We should look into how it's made comfortable for the artist. Because from time to time I pressed save and then tried to publish directly and it got invalidated because the scene was supposedly modified.

from pyblish-magenta.

Mm, I remember, also experienced this.

Something to look out for. Perhaps it's ok to ensure it has been saved at least once. Though it would mean missing out on potentially new nodes leaving without a UUID.

Another alternative could be to add another callback to scene saved, imprint the time at which is was saved. The validator could then take this into account.

Not very clean, just throwing it out as an option.

from pyblish-magenta.

I think we're tackling the issue the wrong way.

Shouldn't the validator just validate that all nodes included in the extraction have a UUID? And in modeling also ensure they are unique? (Two separate validators I assume)

from pyblish-magenta.

Good thinking!

from pyblish-magenta.

Shall we close this since we covered this particular problem from that time with a lot of different solutions?

from pyblish-magenta.