From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
03-25-2009 09:30 AM - edited 03-25-2009 09:31 AM
Hi all
I just made a simple program to make you understand better what am trying to do.
@Ray
Except the Exit button, there are no common buttons which different panels share among themselves.
every panel has a different set of buttons. so again i have to put all the buttons containing in one panel in a cluster and make it visible whenever that panel is active.
that would lead to same problem again.
Ritesh
03-25-2009 09:42 AM - edited 03-25-2009 09:43 AM
Ritesh,
Put the clusters inside the Stop value change case and see what happens. Looks fine to me after doing that, aside from the fact that you can't use references like that with latch actions.
03-25-2009 09:49 AM - edited 03-25-2009 09:49 AM
even if i put the cluster in the "Stop:Value change" , the other 2 buttons(go to page 1 and go to page 2) will still be having the same issue..
Ritesh
03-25-2009 10:29 AM
03-25-2009 12:04 PM
There's actually no need to have a cluster since there are actually 4 unique elements anyway.
Have a look at the attached example (LV8.5.1). There are no clusters and no Local Variable. Code is also simpler, no Case Structure.
R
03-27-2009 02:23 AM
03-27-2009 07:12 AM
Glad you liked it.
One key rule to remember with sw.. (or any design).. Keep it Simple. 🙂