I have a front panel that contains two classes of controls: those that are user interface-related and those that are programming related. The status of the UI-related controls is to be logged into a database when I click the Update button. On the other hand, I really don't want to log the status of the Update button or the error cluster, for example. Is there a method of marking or flagging controls into classes or groups so that an iteration over all controls can take action if the control is flagged? Is there some other way to do this other than enforcing some label/caption naming scheme that has a marker as a flag?

The VIs exist on your system. They've been in vi.lib\UserTags since LV 8.6 and you can easily see that by opening one of them and doing a save as or opening its VI properties dialog. Here's one of Darren's nuggets about this.

LabVIEW

Flagging controls for future actions

Solved!

Author

tst--

I took the extra time to implement this the way you suggested. It was virtually done using the Description as the overloaded flag but now I am a bit smarter about how to do this.

Thanks.

Message 11 of 11

(392 Views)

LabVIEW

Flagging controls for future actions

Re: Flagging controls for future actions