LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Radio buttons all connected to property nodes

Solved!
Go to solution

I don't understand why I should keep the container visible. I really don't want that. I have a full screen of controls with no room for this so I put it on top of everything when and if I need to edit one of my scripts.

0 Kudos
Message 21 of 25
(615 Views)

Ah, OK. Your choice.

 

Typically we advise against overlapping front panel elements because it severely hurts redraw performance and is taxing the UI thread. Maybe you can do a dialog style popup subVI instead?

 

And I still think all you need is a single string control and keep the various version e.g. in a string array. You can dynamically fill the control with the correct content, no property nodes needed!

0 Kudos
Message 22 of 25
(609 Views)

These strings are actually rather long TSP scripts for controlling test equipment. I wonder if I should just load them in from a file instead. Then I wouldn't need to hide them.

0 Kudos
Message 23 of 25
(584 Views)

@RHutchings wrote:

These strings are actually rather long TSP scripts for controlling test equipment. I wonder if I should just load them in from a file instead. Then I wouldn't need to hide them.


Since you had them as controls, I assumed that the operator is supposed to edit them at any time. If they are preformed and irrelevant to the user, they should only live on the diagram.

0 Kudos
Message 24 of 25
(561 Views)

And as I already said, you really only need one string indicator to show the selected script if needed.

 

altenbach_0-1584478304784.png

 

0 Kudos
Message 25 of 25
(541 Views)