Jump to content
Sign in to follow this  

GOOP Class Attributes DVR coercion on classes in package.

Recommended Posts

Hey Guys,


We seem to have come across a rather strange issue when including a GOOP Class inside of one of our VIPM packages.


It seems as though the ConnectorPane tag inside the .lvclass is not getting updated properly for the DVR of the ClassAttributes. So the DVR coming out of "GetClassAttributes.vi" is not the same as the DVR internal to the vi itself. This is due to the whole class getting a name appended to the end of it during the build process.


I have attached some images and as you can see, using the outputs from the VI (DVR/cluster) a coercion is required. However using those same two wires internally requires no coercion. Also, if I copy the DVR into the external VI, no coercion is needed. Also if I change the location of the DVR control, another one, there is no coercion either.


Let me know if you need any more information.


Thanks Guys!


- Paul

Wineman Technology



Edited by Daimones

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.