LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
Showing results for 
Search instead for 
Did you mean: 

Enable "Undo" even after saving the VI!

Instead of saving few versions of the same VI, it would be nice to have "Undo" even after saving the VI.
8 Comments
PJM_Labview
N/A

Good idea.

 

I would also add that "Maximum Undo Step by VI" default value should be changed form 8 to the max of 99. For every new LabVIEW version I install, I end up doing this

TimmTheEnchanter
N/A

THIS ANNOYS ME SO MUCH!!!

 

Thank you for posting!

THailey3
N/A
Status changed to: In Development
 
jdunham
N/A

I'm sure I would find this useful most of the time, but I am a little worried about security.  If something is typed into a VI and I want it gone, whether it's secret, profane, embarrassing, or whatever , I need to have some way to make sure it has been purged.  At the very least the undo cache should be saved somewhere else on the local machine rather than in the VI file itself.  But even if cached separately there needs to be an easy way to clean it up.

 

Microsoft Word had some big issues with this, and now there is a market for tools to clean up your Word docs.  Let's not go there!

GregS
N/A

@jdunham: I had read this (perhaps mistakenly) as retaining the Undo history in the current editing session (i.e. until the VI is closed), rather than saving it with the VI.  My take is that version control should act as the long-term "Undo" provider, so possibly contrary to the initial idea.

AristosQueue
N/A

GregS is correct -- this is just undo for the VI in memory. It does not save the undo stack into the VI. It is going to be the same behavior as, for example, editing a document in Microsoft Word, or a document in just about any other editing environment you can name.

G-Money
N/A
Status changed to: In Beta
Available in NI LabVIEW 2011 Beta
G-Money
N/A
Status changed to: Completed
Available in LabVIEW 2011