LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Edupo

Copy list on LabVIEW

Status: Duplicate

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:Example.jpg

 

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.

 

Copy List.jpg

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:

 

Copy list Help Tag1.jpg

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

 

Copy list Contextual.jpg

 

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?

4 Comments
tst
Knight of NI Knight of NI
Knight of NI

This sounds like an extension of this idea - http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Improved-Clipboard/idi-p/1204563.

 

Also, I should point out that LV 2009 and later already addresses some of these issues by letting Quick Drop index the contents of the current project. This means you can drop items from the project by typing their name (which is not the same as what you're asking for, but handles some of the issue).

 

Personally, I try not to let my projects get to that size. I only have very specific things in the project tree and everything else automatically goes into the dependencies section. If I need an hierarchical view, I have the files tab.


___________________
Try to take over the world!
Edupo
Member

Ok, is the same idea, I don't find it because I don't search the word "clipboard". Sorry for the duplicate.

 

 

I try to do small applications too, but this project is done for a big company that wants a complete application easy to use, and powerful. There is some devices that we must control and there is some actions that the client requires and the user must do without knowing nothing about LV.

 

 

In summary, we need to use labview as a complete application development system and is complicated to handle big projects with the actual tools, is because of that I post this idea. Of course the project is too big, but in this project there is several people involved and we must to cut the work too much.

 

Thank you for the feedback!

tst
Knight of NI Knight of NI
Knight of NI

I didn't mean that I do small apps (although some of them are). I meant that I try to keep the project file itself small, instead of having all the VIs in the project tree.


___________________
Try to take over the world!
Laura F.
Active Participant
Status changed to: Duplicate