11-19-2008 11:48 AM
11-19-2008 01:02 PM
11-20-2008 02:29 PM
Hey all,
This is an interesting discussion that we have going on here. What kind of information is in your control? I think that might help to track down how this might be done.
11-20-2008 04:09 PM
Its quite irrelevant actually. I just want to be able to interrogate an OCX to find the appropriate interface.
Sorry, gotta go. Thanks
Adrian
11-21-2008 09:43 AM
Well, I've looked at the flattened string of the refnums as retreived by the Controls[] and by passing a refnum of the AX control directly. Looks like the actual refnum with type attached contains GUIDs where the one received from the VI's FP does not. There is a common 0x4070 value as the second element that may indicate that the control is a ActiveX container, but other than that, I see no way of mapping. 😞 That sucks!
Attached is the information that I received. Looks like I'm giving up. 😞
11-21-2008 11:21 AM - edited 11-21-2008 11:21 AM
11-21-2008 03:23 PM
11-21-2008 04:10 PM - edited 11-21-2008 04:10 PM
The GUIDs are only on the wire that is attached to the ActiveX refnum DIRECTLY. Thus it contains the type information including the GUIDs.
I want to convert the control refnum that is pointing at the ActiveX container to give me the same type of connector.
Here is the block diagram.
11-22-2008 09:25 AM
As you've found out, when you get the reference via the Controls[] property all you get is a generic reference. Even if you cast it to be an ActiveXContainer all you get is a generic ActiveXContainer. You can cast it to a specific ActiveX control by wiring a (direct) reference to an ActiveX control, but you have no way of knowing if the cast is correct since the casting is likely to give no error.
I don't know if it's possible to do what you want with ActiveX controls. Perhaps Adam may be able to dig something up.
11-23-2008 06:06 PM