Add Don't Save and Remove from Project option in save dialogue

[Simplicity_Jon]

When closing untitled VIs LabVIEW gives you a dialogue which prompts you to Save changes, Defer or Cancel.

 

If you Defer Decision then you have to select the VI in the project, remove it and confirm another dialogue prompting to save changes. This means that to close an untitled VI  is a three stage process. This can be quite annoying when you have just created a small bit of test code that is no longer needed.

I propose having a fourth option in the original dialogue allowing you to not save the VI and remove it from the project and memory.

e.g.

[Jon_Kokott]

I would use this all the time.  

[elset191]

Similar idea for files that have been saved already: Do not save option

[altenbach]

"Don't save and remove" is ambiguous because it could be misundertood as "don't save and don't remove." How about "remove and don't save" or "remove without saving"?

[Simplicity_Jon]

Remove and Don't Save seems much better. Shame I can't edit the original idea

[AristosQueue (NI)]

> Shame I can't edit the original idea 

We don't allow that because people might kudos one idea and then someone edit it to be something else entirely. The comments allow for refinement of an idea over time... In this case, you can use the "Report to Moderator" and ask them to add a note to your original idea that this alternate text might be better.

[tst]

---

@Simplicity Jon wrote:

When closing untitled VIs LabVIEW gives you a dialogue which prompts you to Save changes, Defer or Cancel.

---

I don't see this. When I close an untitled unsaved VI in LV 2009 it is removed from the project and thus from memory. The dialog says Don't Save, so I would say that unless this was changed in a later version, this functionality already exists.

As a side note, normally I also get the defer option, but that's because I'm using the JKI RCF, which has a bug which causes LV to think the VI isn't going to be unloaded even though it is.

[AristosQueue (NI)]

Tst: The behavior is different if the untitled VI is a member of a library (lvlib, lvclass, xctl, lvsc). The library, which is open in the project, acts just like a caller VI would and holds the untitled VI in memory. You have to delete the untitled VI from the library for it to leave memory.

[labview4steve]

what about just a single "Don't Save" button as well or instead  (i.e without the remove from project option).

or perhaps a tick to also remove from project

So this will simply cause the VI to be RE-LOADED from the disk as it was when you exit from the VI edit screens.

For example:

I quite often do tests on some of my VIs.. one project has 500 vis - but I often don't want to be able to re-open the entire project all the time.. many times I will just press defer because there is no other option then later I'm confused as to what exactly has changed... only to find that it only had some wires had been moved etc and no data change - its a COMPLETE PAIN.. why can't we have a simple "Don't Save" which then will RE_LOAD the VI into memory as it was stored on disk - this should be pretty simple to implement...

[tst]

> The behavior is different if the untitled VI is a member of a library

That explains it. I normally don't create untitled VIs in libraries.

> So this will simply cause the VI to be RE-LOADED from the disk as it was

This idea is about UNSAVED VIs. To reload a VI from disk you can click Cancel and then select the VI's File>>Revert option. Also, elset's link above points to an idea about an explicit Don't Save.

[AristosQueue (NI)]

> This idea is about UNSAVED VIs.

Actually, this is about UNTITLED VIs, i.e., those htat have never been saved. Unsaved VIs are just VIs that have docmods.  The moderator has changed the single word in the original idea from "unsaved" to "untitled" to make sure we're all talking about the same thing.

> So this will simply cause the VI to be RE-LOADED from the disk as it was when you exit from the VI edit screens.

User elset191 above mentioned another similar discussion thread. Follow that link and find the post from me that discusses the problems with the reload variation. I won't discuss it further here since it is off-topic -- this thread deals with untitled VIs and that feature affects unsaved VIs.