09-23-2025 08:29 AM
Hi GerdW,
sorry if i have learnt LabView by myself and i missed some Basic information. I have always thought the comunity as a place to find inspiration to go deeper in my knowledge so thank you for all the points that you have highlighted. I came up with something like this:
The only thing is ho can i disable the not used elements? in the picture are the ones with an empty Channel list.
Thank you very much for the help and the kindness!
Best Regards,
Zuc
09-23-2025 08:41 AM
Hi Zuc,
@Zuc_lab2 wrote:
The only thing is ho can i disable the not used elements? in the picture are the ones with an empty Channel list.
Again basic LabVIEW knowledge: in an array ALL elements share the SAME properties.
This results in: You cannot disable some elements in an array!
There's a reason for the idea/suggestion in my previous message…
09-23-2025 10:09 AM
@Zuc_lab2 wrote:
Hi GerdW,
sorry if i have learnt LabView by myself and i missed some Basic information. I have always thought the comunity as a place to find inspiration to go deeper in my knowledge so thank you for all the points that you have highlighted. I came up with something like this:
The only thing is ho can i disable the not used elements? in the picture are the ones with an empty Channel list.
Thank you very much for the help and the kindness!
Best Regards,
Zuc
It's easier if you keep it 1 dimensional
09-24-2025 01:27 AM
Hi Yamaeda,
I thought about your advice but the problem is how to manage the possibility to reach also 100 elements since the main front panel that I wish to have is something like:
I’m trying to reduce at minimum the dimension of the cluster but still trying to find also a smarter way.
In the meanwhile do you know any option to live accessible by the scrollbar also active elements of the array? Because my code always shows all the active elements but I need to keep the size of the array in the front panel fixed.
Thank you for the help!
Best Regards,
Zuc
09-24-2025 02:43 AM - edited 09-24-2025 02:46 AM
Hi Zuc,
@Zuc_lab2 wrote:
how to manage the possibility to reach also 100 elements since the main front panel that I wish to have is something like:
You could show scrollbars for those array controls.
You can even show/hide them depending on the number of channels…
(This will give a bad UX when the user has to scroll too much!)
@Zuc_lab2 wrote:
I’m trying to reduce at minimum the dimension of the cluster but still trying to find also a smarter way.
In the meanwhile do you know any option to live accessible by the scrollbar also active elements of the array? Because my code always shows all the active elements but I need to keep the size of the array in the front panel fixed.
You can:
This will reduce the pixel size of each cluster.
I recommend to use System controls to make the UI more "look like standard OS".
I still recommend to use a MCLB to show all available channels to the user. (The MCLB also supports scrollbars to show larger lists.)
I also recommend to not use a LabVIEW error indicator to show errors to the user!
I would use a simple string indicator instead, showing some formatted text in case of errors… (This will reduce needed UI space a lot!)
09-24-2025 04:04 AM
Hi GerdW,
That idea can fit my need! you're suggesting something like this:
So from the list box i take the information i need.
The client ui idea is to have all boolean button to press, a huge ammount to display when needed.
But how the cluster can change based on the MCLB? Can you show me a simple example?
Thank you very much for the help!
Best Regards,
Zuc
09-24-2025 04:11 AM - edited 09-24-2025 04:12 AM
Hi Zuc,
@Zuc_lab2 wrote:
But how the cluster can change based on the MCLB? Can you show me a simple example?
Generic advice:
09-26-2025 04:46 AM
@Zuc_lab2 wrote:
Hi Yamaeda,
I thought about your advice but the problem is how to manage the possibility to reach also 100 elements since the main front panel that I wish to have is something like:
How would this 1D array version work out?
09-29-2025 09:44 AM
Hi Yamaeda,
Due to time issues, I have choosen to create a certain number of cluster and hide the not used ones by property nodes in a separate VI respect to the Main one.
The front panel is something like this:
while the VI uses event and property node to manage the clusters input:
It isn't so smart for a lot of switches but this was the fastest solution right now.
Thak you for the help!
Feel free to add any advice or best practice to improve it.
Best Regards,
Zuc