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!
cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
riley.ilieva

Enqueue Enum Message

Status: New

We use Queued Message Stage Machines a lot and often send messages through API calls. In a state machine I prefer using enums to determine the state and in the QMSM that would be useful too because sometimes a typo in a message in an API call stops it from working. 

 

However, the Message Queue functions accept string only. 

 

 

image.png

 

Even if we make changes to the message cluster or make the VI polymorphic but we would then need to do it every time we are setting up a new machine with LabVIEW. Would this be useful for anybody else? 

image.png

 

 

 

 

2 Comments
wiebe@CARYA
Proven Zealot

Useful?  Maybe. Feasible? Not really.

 

There is no way to make a VI that accepts (only) any enum.

 

The VI would have to accept a variant, which would be error prone and unclear, or the VI has to be a vim, which would be error prone and unclear.

 

thols
Active Participant

Why not just make such a VI that has your enum type as input?

 

(where are those VIs anyway, can't find them in LV)

 

(I would use channel wires instead, they can hold any data, but that's just me)

 

 

Certified LabVIEW Architect