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!
Showing results for 
Search instead for 
Did you mean: 

Globals that can be created during run-time and accessed by name (i.e. native Current-Value-Table/VIRegisters)

Status: Declined

Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.

There are lots of people who are working on solutions to be able to dynamically create a storage space for a variable and access it by its name. Publically we have the Current Value Table and the VIRegister, but behind the scenes I'm sure people are recreating this wheel quite often (instatiation of functional globals e.g.). Shared variables offer some of this functionality, but it is not quite the same, nor is the way they are accessed as user friendly as the CVT/VIRegister.


The problem when implementing these with the existing primitives however is the fact that no matter how much you try the solution will have performance issues and be less user-friendly due to lack of full polymorphism. People will continue to improve their solutions within the limits of the tools they have available, but why not provide an optimal solution for such a common architectural element instead - by adding this as a set of primitives/in-built functions?


(The tag engine of the DSC module might be a close relative to this, but is it too close?)

Proven Zealot

I don't like this idea. My thoughts on the issue are posted on this thread in the LAVA forums.


Active Participant

So you do not like and/or see the use for things like the CVT or a tag engine? I get a lot of good work done in LabVIEW with such tools and I have yet to see any alternatives that provide the same flexibility and scalability. If they existed I would not be stranger to using them, by all means, but where are they? Why do so many people still strive to create by-reference solutions in LV when the alternatives are so much better? 


All tools can be misused, but even the most dangeous ones can be invaluable in some cases. It is of little help to not have them at all.

Trusted Enthusiast
Trusted Enthusiast

I tried to get a discussion started on this during Christmas break but with little success... Good luck!

Proven Zealot
Status changed to: Declined

Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.

DNatt, NI