Diadem 2017 forced save as?

[RussellSenior]

 Whenever I press the new button in any panel and I have unsaved data (Navigator, View, Report) I am presented with the "Save As" dialog and I MUST save the work before I can continue.  I am not given a choice to not save anything.  Is there a setting for this?  I would like to be able to clear the portal, or clear the view panel without saving my present work. 

[RussellSenior]

It must be something in one of my scripts.  After restarting, I noticed it works normally.  After running a few scripts, it stops working again.  I also noticed that some dialog boxes don't pop up anymore after running one of them (such as script error dialog boxes).  I will have to see if I can figure out exactly what and where. 

[ChaosYeti]

I never had a problem like that. Have you reported that as a bug to NI?

[RussellSenior]

When I have a reasonable idea of what is causing it, or a way to repeat the problem, I report the bugs.  This one is a bit intermittent though, I run the same scripts every day, and it does not always happen. 

Although, while solving another issue I came across the variable "CmdNoWarningDisp", and the description seems to describe what is happening.  Perhaps that variable gets set to False somewhere in the bowels of my scripts...

[ChaosYeti]

Good luck to find that issue!!

Yet, I just learned, that the newer versions tend to do funny things.

Half a year ago I did some script with DIAdem 2015 on Win7, and it worked for everyone who used it. Now I have a colleage using it on Win10 with DIAdem 2017, and he seems to get random failure messages now and then after a while. They disappear after restart. We haven't found the reason for it yet.

Nothing's worse than a failure that occurs at times at diffent situations.

[Chris_P_SD]

I have experienced this same issue as well with DIAdem 2017 SP1 (64-bit) running on Windows 7.  Once this behavior starts, I also noticed I cannot close any Script tabs, e.g. "NoName(1).VBS*" without being prompted to save and actually saving the file.  I then subsequently delete the saved .VBS files in Windows.