@samPT7WG wrote:
Hi, we have an issue in our studio where if someone has saved a scene and immediately hits "close" they are sometimes asked to save the scene again.
Is there any way to find out what is triggering the dirty flag? (other than the undo list)
Firstly, it is not at all necessary that the scene needs to be saved (meaning save flag is dirty). It's easy to check - run
getSaveRequired()
If it's dirty anyway... Most likely that some script is using one of general callbacks (file notifications) to do something what makes scene dirty... more likely is #filePreSave, #filePostSave, #filePreSaveProcess or #filePostSaveProcess callback.
You can look them all using:
callbacks.show()
find suspicious ones, and you can technically remove them at your own risk.
If this does not help, then we can look for something else, as well as remove the dirty flag 😉
By the way, check Undo Buffer after "save" the file. Do you see any new records?
