Jump to content

Private Class Corruption when migrating to 8.5


Recommended Posts

FYI: From NI tecknical support

Thank you again for your patience in all of this and thank you for

posting the more complete file compilation of the 8.2 version of your

code. The person who was working on this issue in R&D found another

Corrective Action Request that is similar to the issue you are

having. The reference number for that is 4CG9B3J1. This is set to

be fixed in the next release of LabVIEW. The problem seems to be

with the private data class loading the first time in LabVIEW 8.5 and

becoming corrupted. Therefore the workaround is to load the private

data control that might be associated with a lvclass and open the

front panel and resize any control in the private data cluster. This

puts a docmod on the VI so the class knows to update the saved image.

I believe R&D has verified this with the Shack_Hartman.lvclass since

that one was not already corrupted in 8.5. With the Variable Token

class that you have loaded, it has already become corrupt so nothing

can be done. This is why we needed more files in the project than

you had originally provided. I wanted to provide you with more

information on this problem. Again I apologize for the inconvenience

this has caused you but we definitely appreciate the feedback so this

can be fixed for the next release. Thanks again for contacting NI!

Link to comment
  • 3 months later...

This bug only affects LVClasses that use certain data types in the private data cluster. Those include the DAQ Tag data types and certain refnum types includeing VISA, DAQ and IVI refnums. They do not include any VI Server refnums (app, VI, ctrl), nor queues, notifiers, files or datalogs. I know that isn't an exhaustive list of refnum types, but it covers the big categories.

Link to comment

Join the conversation

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

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
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.

×
×
  • Create New...

Important Information

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