09-21-2005 04:56 PM
09-21-2005 07:57 PM
Hello,
One way to determine if it's a control or indicator is to right-click on it in
either the front panel or the block diagram and you'll either see something
like "hide control" if on the block diagram or "change to
indicator" on the front front panel. This is a quick way to
determine that. As far as to determine whether it’s a connector, your
best bet is to right click the VI icon in the front panel to bring up the
connector pane, and cycle through clicking on the connected items. Its
sort of an exhaustive search, but you probably won't have too many to go
through so it shouldn't be too bad.
Hope this helps a little; let us know if we can help out anymore!
09-22-2005 01:21 PM
@Travis M. wrote:
One way to determine if it's a control or indicator is to right-click...
Right clicking certainly can't be done programmatically. You are not suggesting I try to use some click based automation tool?
@Travis M. wrote:
Its sort of an exhaustive search, but you probably won't have too many to go through so it shouldn't be too bad.
Trust me, there are too many to go through.
09-22-2005 02:46 PM
@terminalman90 wrote:
... I am looking for a way to determine if the control is a connector for the VI or not. This information is available to (and displayed by) the context help window. Is there a hidden property of the VI that gives me access to this information?
terminalman,
You may want to check out the discussions on certain properties in the LAVA forum here.
Read all the warnings, etc. You may not find an existing thread on what you want, but it's there.
09-22-2005 05:07 PM
Thank you Donald. That was very useful information. I found properties that would enable me to accomplish my task.
Another simpler (?) solution would be to use the print functions NI provides to create html documents. This function prints out all the information I require for documentation (and lots I don't want too). It doesn't give me complete control on the output, but I suppose I could take the html code output and post process it into my own format.
09-22-2005 05:07 PM
09-22-2005 06:36 PM
terminalman90 wrote:Another simpler (?) solution would be to use the print functions NI provides to create html documents. This function prints out all the information I require for documentation (and lots I don't want too). It doesn't give me complete control on the output, but I suppose I could take the html code output and post process it into my own format.
I understand the "(?)" ... all depends on what you want in your documentation.
But just in case you've missed it while trolling through LV's properties and methods: you do have quite a bit of programmatic control (well-documented and supported by NI in this case) over what gets printed out to HTML/whatever through the Application: Printing:Custom properties.
Good luck.