Is there any way to stop the save disk icon from turning on even if I switch documents? It's really annoying and makes me wonder if I already saved or not and some documents are huge so it takes time to save them.
It must have something to do with how the document is monitored in terms of the 'dirtyiness' of it and some things are picked up and registered as a dirty doc when it really isn't. Anyone dirty?
If memory serves there was a discussion on that, there was a difference between files opened from other computers verses files reopened on the originating computer. Something to do with fonts I believe. I believe something to do with background tasks also. Old age and too many issues to track is getting to me.
I use the following as a button I've assigned it to only when I am certain I have no changes to save.
Its easy to check for sure because I always have the Undo Manager open on a second monitor (along with like 8 other dockers, hah).
Have you tried checking with a VBA macro to see if it reports that the document is dirty?
That's not a solution, but I'm curious whether there are ever times where that disagrees with the display of the "save" icon and/or the asterisk after the filename in the title bar.
I've pin-pointed that page-changing (moving from page to page) is causing the dirtieness. How can I fix this?
That's interesting. Its also not the case for me. Just tried it.
I believe the thread David Millisock was refering to above was this one I also read a while back:https://community.coreldraw.com/talk/coreldraw_graphics_suite_x7/f/coreldraw-x7/49753/do-you-want-to-save-after-no-changesIn there, someone talked about Callout Shapes being the culprit. If I remember, that wasn't the case for me. One reason being that the issue happens with me and I don't use Callout Shapes, but I did try to make it happen that way and it didn't. It always happens to me with documents I've done nothing with at all, except for zoom and pan. Undo Manager has no activity, yet I finish viewing and close the document... "Save changes?". From a user's end, I don't see how it could be fixed other than the Application.ActiveDocument.Close.