08-10-2017 10:24 AM
Hello,
I'm trying to port the libraries I made in a previous version of LabVIEW (2014). I can create the library but the menu is all messed up. So I am trying to edit my palette set, and every time I try to execute it LabVIEW crashes.
Is there a reason for this?
Do I need to delete my user library?
08-10-2017 11:23 AM
Never mind... I deleted my library objects and now I can edit the palette set.
08-10-2017 12:28 PM
Ok, after further work I can edit my palette. But, once I recompile my library and throw it in the user.lib folder, everything crashes again.
What's more, I have no User Library option in the palette. I tried to add it by turning it on, but it doesn't even appear unchecked in the available options.
Something is screwy here in 2017...
08-11-2017 08:21 AM
Hello,
I'm a little confused on what exactly the issue you are having is. Would you be able to provide a screenshot of the crash you are seeing and step-by-step instructions to reproduce said crash?
08-11-2017 09:32 AM - edited 08-11-2017 09:33 AM
Sure.
If I include my library, and I open a new VI, and go to tools -> advanced -> edit palette set, the palette set never loads and LabVIEW becomes unresponsive.
I am using Windows 10, if that matters.
I cannot share the library, sorry. But it does work fine in 2014.
08-11-2017 09:51 AM
Backward compatibility is usually where issues arise, not forward compatibility. Without being able to see the library there is not much more I can do troubleshooting wise. I will search internally for any know issues or crash reports associated with this behavior.
08-11-2017 11:20 AM - edited 08-11-2017 11:21 AM
I can share this one. It does the same thing.
I opened the project in 2017, recompiled it and added that compiled library to the 2017 user.lib