Francois Normandin Posted April 2, 2015 Author Report Share Posted April 2, 2015 hmm. Looks like it was meant to remove previous releases of Control addon class but I might have forgotten to change the namespacing. This looks like a self-conflict. Can you let me know which version you are using? I don't have 2011 installed as your profile suggests, but I'll try to reproduce the issue on a newer version and come up with a new package or a solution. Quote Link to comment
Chris Posted April 2, 2015 Report Share Posted April 2, 2015 Thanks Francois for updating the four expansionpacks to a VIP package - you're a real saint Chris 1 Quote Link to comment
Francois Normandin Posted April 2, 2015 Author Report Share Posted April 2, 2015 Manu, let me know if this solves the dependency conflict: (v1.4) https://lavag.org/files/file/120-ui-tools-addon-control-class Quote Link to comment
Chris Posted April 2, 2015 Report Share Posted April 2, 2015 Hi Francois, FYI When I installed the four expansion packs the Glassweb and System Styles had all buttons present, but there were a number missing in each of the sub-palettes for the Outlook and Vista Styles - for example.... Chris Quote Link to comment
Francois Normandin Posted April 2, 2015 Author Report Share Posted April 2, 2015 Ah. I renamed a bunch of controls with duplaicated names and didn't reload my package build file after I fixed them. It must be linking to the previous name. I'll have a fix in a moment for both packages. Outlook package updated to 1.1.0.3 Quote Link to comment
eberaud Posted April 2, 2015 Report Share Posted April 2, 2015 Hi Francois, Yes it did fix it! (I'm using 2014 right now, but still 2011 in general) I had to restart VPIM to get rid of the conflict icon though. But now everything looks good! Thanks 1 Quote Link to comment
Chris Posted April 7, 2015 Report Share Posted April 7, 2015 Thanks Francois for fixing up the missing Outlook buttons. You got 99.99% of them fixed I just found one button missing in the Media Palette called "outlook_video.ctl" Chris Quote Link to comment
Francois Normandin Posted April 7, 2015 Author Report Share Posted April 7, 2015 beuh... I think I'll leave that one until the next version Quote Link to comment
Antoine Chalons Posted March 15, 2019 Report Share Posted March 15, 2019 After installing the latest version with VIPM on my LabVIEW 2018 SP1 32 bit, every time I try to run LabVIEW, it crashes. I deleted the folder C:\Program Files (x86)\National Instruments\LabVIEW 2018\project\UI Tools and then no more crash. Any idea? Quote Link to comment
Antoine Chalons Posted March 15, 2019 Report Share Posted March 15, 2019 Ha, I think I found the issue, I should have let VIPM mass compile the package after installing it. I had to move "Create control.vi" out of the C:\Program Files (x86)\National Instruments\LabVIEW 2018\project\UI Tools\Control Generator, open it, mass compile it place it back and now it all works fine. Quote Link to comment
Francois Normandin Posted March 15, 2019 Author Report Share Posted March 15, 2019 Bonjour Antoine, I'll take a look at this. Can you tell me which version you've installed? Quote Link to comment
Antoine Chalons Posted March 16, 2019 Report Share Posted March 16, 2019 It's 1.4.0.15, if you need any help in trying to reproduce this behaviour you can PM me. Quote Link to comment
Antoine Chalons Posted March 25, 2019 Report Share Posted March 25, 2019 I reported this issue to NI, they created a CAR 732888. LabVIEW should handle broken stuff in ~\LabVIEW XXXX\project\ subfolders. Quote Link to comment
davizur Posted May 2, 2019 Report Share Posted May 2, 2019 Thanks Antoine for your workaround to fix the Labview crash after installation of the 1.4.0.15 version on also LV2018 SP1. Your tip just helped me, too. I had Labview crashing also with the previous 1.3.0.12 version installation on LV2015 SP1, there for some reasons it helped to install all required packages package by package with the JKI VIPM. Apart from that recent installation issue the Control class UI Tools addon is a fantastic tool, and we use it frequently. Thanks François! 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.