LabVIEW Idea Exchange

Hello, I'm searching about this topic in the forums, but I find no ideas about this, if I repeat the idea please tell me.

I'm working with LabVIEW from time ago, but I've noticed that when you have a large Project is complicated to work with it. I will explain myself:

Here it is my last project (right), you can see that it have a lot of directories and a lot of classified data, controls, vi's and some more stuff. I hope you are familiar with it. Well, you will work with it for a lot of time, but when you want to go fast you need to access to some controls or global variables files a few times, don't you?. This is annoying with the actual interface, because of the nesting in the virtual directories. Some kind of favorite system is needed, but instead of that I have another proposal:

Copy list.

Let me explain this idea. You can have in the project explorer, for example, integrated another tab called copy list that can be like this.

Ok, every time you do a copy action the object that you copied is added to this list classified as you can see. Now you are able to drag and drop items very fast without searching on the project explorer, you can center on the work (I've noted that I expend a lot of time searching on the project explorer tree my next control or vi to use).Well, let's see the really advantages that I think can be helpful.

If you stop the cursor on a element you could see all the related information easily:

   But this is not the only shortcut to access your "most used" stuff, I do another image to show you the options:

Now this is the real advantages:

• You can copy to the clipboard elements easily (as property node or invoke node) and without searching the control or terminal
• If a control is used a lot of times you can fix it on the copy list and you can put it in order. (The fixed elements can be marked in bold and can be in the firsts positions of the list)
• Of course you can remove a element that you don't use.
• If you must to go home you can save the copy list to get it easily tomorrow.
• An extended help is useful in this list.
• I think that a rename option is helpful too.

You can define the length of the list to achieve some memory optimization (but with the actual development computers I think that this is not a problem).

But for this price I think that this can be a great tool to work fastest on LV.

What do you think?

Often times, I have a set of code in a for loop that takes a while to complete, so I put in a progress bar on the UI.  The problem is the progress bar defaults to 0-100 range, and my for loop normally does not have 100 iterations. 

So.... I can either rescale the progress bar to the number of elements, or I can use the "N" and "i" to calculate the percent complete and use that.

Since I like to keep my progress bars as 0-100 (since that works nicely to also show a percent complete) and % complete is useful elsewhere, I generally always end up calculating % complete of my for loops.

Well, why can't NI calculate this for me automatically???  Something like expanding the "i" iteration counter in the loop also have a "%" box right next to it.

Example shown below should probably wire as a double instead of an int, but you get the idea!

When I save a vi for a previous version then the next time I open that vi and close it LabVIEW prompts me to save it because it was converted from a previous version. I should be able to open it, make changes, and save it again with LabVIEW remembering what version I wanted it saved for. Maybe the version could be a vi property?