Jump to content

Andrew Casalenuovo

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by Andrew Casalenuovo

  1. The key combination for invoking Quick Drop (CTRL+SPACE) instead invokes Design Palette. Cannot workaround it, so I am uninstalling Design Palette. This is in LV2017, JKI Design Palette 1.0.5.196
  2. Good morning, I'm in the midst of a full uninstall-reinstall due to some versioning conflicts between LV 2017 and 2021, missed deleting VIPM I guess because when I went to start reconfiguring my environment, it said I had all the packages that I had before uninstalling. So I start hitting Uninstall and then reinstall on the various packages in order to set it all up again. But then uninstalling something like OpenG that other packages depend on uninstalls those dependent packages. I've since learned to hit Downgrade then Upgrade, but still, It's been a whole thing. All of that to say, I think there should be a Repair Package option on the Package Information window, that has the functionality of redoing the install to make sure every VI and CTL of that package is in its proper place on disk, without anything happening to the dependent packages. If that operation could be made available on the main VIPM window to give us the option to mass-click packages and do that to all of them in series, even better.
  3. I'm late posting this. If you haven't already figured it out, Cybereason does not like newer versions of LabVIEW. What we've needed to do is build an exclusion list for the Cybereason ActiveProbe not to run on I believe.
  4. We are also having issues with VIPM not running on our development computers due to Cybereason ActiveProbe. But it's even worse for us... We have LabVIEW 2019 Runtime in our Software Center, which allows anyone in the company to install it without admin rights. This has been done so we can give small executables to people to use, ones that don't need VISA, DAQmx, etc. Runtimes. Well, everything was fine a couple weeks ago but now ALL of those small programs load up with the same message, "The VI is not executable..." Since VIPM 2020 uses LV19 Runtime, this makes sense. But wow is it a pain. We're also in talks with IT as to what the core issue is and what course of action to take.
×
×
  • Create New...

Important Information

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