Spurious VIs linked to button ?

[malosh]

Working with LabVIEW7.1 I encountered the most puzzling fault, which I would very much like to understand the source of it, as well as find a suitable bypass.

The basic problem I was dealing with is identifying the type of some refnum. This was done by casting it to the tested type, then using the error output of some property node to decide whether the cast was successful.

However, the following scenario yields some bizarre results:

• Casting a button refnum to a VI refnum.
• There is a 'Value Change' Event handle for this button.
• The 'Details Display Dialog.vi' is in memory.
• Building the application using the 'Enable ActiveX server' option.

Running the VI in my development zone indeed generates the expected error, but the resulting application does not generate this error as it successfully casts the button to 'Details Display Dialog.vi' !

I've attached the reduced VI together with the related executable.

 With great hope that someone has a cool answer

   Malosh

[TCPlomp]

Why do you use typecast?
You can use 'to more specific class' OR the Class name property:


These will give you more control over the control type.

Ton

Message Edited by TonP on 08-11-2006 12:42 AM