11-10-2009 05:11 PM
When working with a sub-VI which has terminals connected to hidden controls is there a straight-forward way to find the terminals on the block diagram?
I click on the terminal and an outline appears on the front panel but when I try to click on that outline I can not unhide the control.
The only way I have discovered to find the terminal of the connected control is just check each terminal on the block diagram which looks like it might be connected.
I'm using LV7.1 but also use 8.5.
Thanks,
Davey
11-10-2009 05:40 PM - edited 11-10-2009 05:41 PM
I'm not sure if I have the exact gist of your question, but...
In order to unhide a control, right-click on its terminal on the block diagram and select "Show Control" from the drop-down menu. The hidden control will no longer be hidden, and will show up on your front panel.
11-10-2009 07:15 PM
Yup -
as Diane said thats the only way t do it!.... Its easier to "hide" controls by placing them off the visible area of your UI. but sometimes its necessary to use a property node to show or hide them so the user isn't too distracted. (Hint: show all controls during the clean-up routine)
11-10-2009 10:05 PM
If I understood the premise of the question it sounds like you have controls/indicators wired to the VI connector pane, but for some reason these controls/indicators are hidden. If this is a VI you wrote slap yourself. If this is a VI someone else wrote, go slap them.
One way that you can find the terminals on the block diagram by performing a search by text. The context help will show you the names of the controls/indicators. The only problem with this approach is that if the control/indicator has the caption visible rather than the label, then the context help will show the caption, not the label.
Another method is to use scripting. Not sure if it's worth the effort for just one VI, though.
11-11-2009 08:15 AM
11-11-2009 08:48 AM
Thanks all. I should have used the terminology "wired" rather that "connected" in my original question.
Smercuio_fc,
Your suggestion should get me through this project, thanks. I might use this as an opportunity to learn scripting, if anything to unhide all the controls (there are many VIs). Not my project so no self-slapping in order. I do wonder how many other bad habits I'm picking up working in this code though.
Jeff,
Not sure what you meant by the "clean up routine"? Were you referring to an option in LV to show all or just a general procedure which everyone performs when writing LV programs?
Regards,
Dave
11-11-2009 08:57 AM
smercurio_fc wrote:If I understood the premise of the question it sounds like you have controls/indicators wired to the VI connector pane, but for some reason these controls/indicators are hidden. If this is a VI you wrote slap yourself. If this is a VI someone else wrote, go slap them.
![]()
One way that you can find the terminals on the block diagram by performing a search by text. The context help will show you the names of the controls/indicators. The only problem with this approach is that if the control/indicator has the caption visible rather than the label, then the context help will show the caption, not the label.
Another method is to use scripting. Not sure if it's worth the effort for just one VI, though.
Before we get all slap-happy I have to ask...
If I have a sub-VI which is set for Print on completion and the controls in/out for the icon connector are NOT supposed to show up on the final report, isn't setting those objects as hidden a viable option?
Ben
11-11-2009 09:14 AM
davey31415 wrote:
Smercuio_fc,
Your suggestion should get me through this project, thanks.
Be careful implementing Smercuio-s approach. You might get arrested for slapping the original developer
![]()
Jeff,
Not sure what you meant by the "clean up routine"? Were you referring to an option in LV to show all or just a general procedure which everyone performs when writing LV programs?
Most applications can be abstraced to have the following sections, Initialization (Set parameters, open referances, etc..) Do something useful (make measurements, operate on data, etc...)and Clean-up (close referances, save parameters, reset UI states, exit, etc....) Reseting control states is a good idea if you are still developing the code so that when youtest your application and need to make changes the vi is left in a condition that makes it easy to work on.
11-11-2009 10:22 AM
Ben wrote:
smercurio_fc wrote:If I understood the premise of the question it sounds like you have controls/indicators wired to the VI connector pane, but for some reason these controls/indicators are hidden. If this is a VI you wrote slap yourself. If this is a VI someone else wrote, go slap them.
![]()
One way that you can find the terminals on the block diagram by performing a search by text. The context help will show you the names of the controls/indicators. The only problem with this approach is that if the control/indicator has the caption visible rather than the label, then the context help will show the caption, not the label.
Another method is to use scripting. Not sure if it's worth the effort for just one VI, though.
Before we get all slap-happy I have to ask...
If I have a sub-VI which is set for Print on completion and the controls in/out for the icon connector are NOT supposed to show up on the final report, isn't setting those objects as hidden a viable option?
Ben
Well, of course, Ben. My comment was not meant to be taken seriously... hence the smiley happy icon. To respond to your question in a more serious matter, though, there's always exceptions to rules. That's why they're rules - they're meant to be broken. Otherwise they wouldn't be rules. It's a strange state of the universe, isn't it? Although, one could probably just place the control behind another object. That sort of hides it, doesn't it?
11-11-2009 10:30 AM
smercurio_fc wrote:..., of course, Ben. My comment was not meant to be taken seriously... hence the smiley happy icon. ...
My post was focused on two issues.
1) "teasing the lions"
2) Getting you to admit there is an exception. God willing some day soon you will be sporting a new outfit and the noobs of the future will be reading your words like they are gospel. If we don't nip these "rules" in the bud before we know it "our untended garden will go to seed". (Praphrase from Hamlet).
Ben