I have a definition that is entirely user-facing and doesn’t require any GH manipulation whatsoever. That said, the file modifies itself on a regular basis – and therefore causes the Modified flag to be set on the file, despite not changing functionally. When users quit Rhino (or Grasshopper), the user is prompted whether to save the document. It is confusing for them, as they are not Grasshopper users and don’t know what to do.
Is there any way to prevent the dialog from appearing for this file? I have tried attaching a listener to the RhinoApp.Closing event, but I get an error because the GH_Doc gets unloaded before I can create a GH_DocumentIO on it to perform a save. I also still get the multisave window.
An idea solution would either Save the document at the right time so that the multi-save dialog doesn’t appear, or modify the Modified flag so that multisave does not appear (this does not appear possible). Either way, I don’t care whether the document is saved or not.