Jump to content

Ryan Vallieu

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0

About Ryan Vallieu

  • Rank
    LAVA groupie

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since
    2003

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I created a separate VI with the Scripting node and got the same Error 42 when modifying the INstanceInfo. I believe it was because there was just something wrong with the original PolyVI - I recreated it programmatically with scripting code, then used the tool, and now I am not getting an error on modify/save in the tool. Something must have been corrupt.
  2. Even more strange. Started a new Poly VI from scratch in Documents folder. No VIs added to it, just created New in LV 2016 and saved. Opened tool, added two VIs to the list, click Save VI - get Error 43, operation cancelled by user!? I didn't cancel any dialog.
  3. I should have thought to check that, but since the LabVIEW Editor was saving it fine it didn't occur to me. I will check. EDIT: It won't even let me save a new copy in the Documents folder - same error. Windows 7 evidently doesn't let Administrators remove Read Only from the Microsoft description - odd, even using the cmd prompt to attrib -r c:/<folder> on the folder and trying again to save yielded error 42. I will try a separate version of the Polymorphic Scripting node in some test code in LabVIEW to see if I can replicate the issue.
  4. Hmm. When trying this out an doing a save after an Edit - I am given Error 42. Error 42 Occured at Property Node (arg 1) in Polymorphic Editor.lvlib:Apply Changes.vi->Polymorphic Editor.lvlib:PolymorphicGUIEditor.vi
×
×
  • Create New...

Important Information

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