Close edited VI: Option to Revert Changes in the "Save Changes?" Dialog

[dthor]

When closing a VI that has been edited, the "Save Changes?" dialog pops up asking if we'd like to save, defer the decision, or cancel the close operation. There should be a 4th option, one that reverts the VI to the previous saved state. It could be called Revert or Discard Changes, that doesn't matter.

When I was first starting with LV, it took me quite some time to remember to File -> Revert before closing a subVI that I didn't want saved. Heck, I still do it once in a while. I'll make changes to a subVI that end up vastly modifying the output (just to test something, let's say), and I'll close the VI and Defer the save decision. Then I'll run my toplevel and wonder why the heck my output looks so wrong

[JackDunaway]

Before this Idea gets closed as a duplicate, I just want to say I think it's a good idea. Yes, there may be "too many options for new users", but the ability to perform this action outweighs this cost.

I'll sneak in a +1 before Kudos are disabled.

[dthor]

Haha thanks Jack

[LuI]

Playing with productive code is playing with fire! Either make a copy of a vi you are going to play with. Or use versioning!!!

Greetings from Germany!
--
Uwe

[dthor]

I do use versioning, which is one reason why I don't mind playing with production code. Also, I only deploy with executables, I don't release a new executable without thorough bug checking, and there are only 6 locations that use my code, all of which I have easy access to if a bug is found.

Sure, it may not be the best practices around, but it works for me. 

EDIT:

Also, not that I'm complaining, but why hasn't this been marked as a Duplicate yet?

[G-Money]

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Do-Not-Save-Option/idi-p/971687

[G-Money]

I am closing this idea as a duplicate because the other idea incorporates this functionality and has more visibility with R&D with higher Kudos.