I have been having a weird issue for a while now with both vs 14 and 15 on multiple computers--when I write some code, run it, and then close out and click "Don't save changes"... it saves the changes anyway.
I did a simple test where I created a new macro, saved it, reopened it, typed another line and closed it without saving--didn't save the added line. However, if I add a line and RUN it, click don't save, and reopen it, the line is still there. Also, getting updated last modified dates on scripts I just open, run, and don't even add anything to, which I don't ever remember happening before. Any ideas?
Example--write first two lines and save, then reopen, type next two lines, RUN IT, and DON'T SAVE, those lines are there when reopen anyway:
//unwanted autosave test--save this
Message>test--save this
//don't save this and below
Message>test don't save this part
Anyone else experiencing this...?
Moderators: Dorian (MJT support), JRL
- Marcus Tettmar
- Site Admin
- Posts: 7395
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
- Contact:
Re: Anyone else experiencing this...?
In the editor menu click on the Debug menu and uncheck Save on Run/Debug.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
Re: Anyone else experiencing this...?
Thanks Marcus. Just know it..Marcus Tettmar wrote: ↑Tue Mar 24, 2020 8:20 amIn the editor menu click on the Debug menu and uncheck Save on Run/Debug.
Re: Anyone else experiencing this...?
I never encountered this situation, but created it, and yes, it did save the changes although I specified the opposite.
The run/debug fix solves the issue though.
The run/debug fix solves the issue though.