Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


cmal last won the day on March 12 2018

cmal had the most liked content!

Community Reputation

1 Neutral

About cmal

  • Birthday 12/30/1979

Profile Information

  • Gender
  • Location
    Austin, TX

Recent Profile Visitors

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

  1. Thanks, Jim. That's great news. I'm not sure whether it addresses Fab's concerns, but it does address mine. I'll let you know if I encounter any issues with VIPM 2017 for Linux. -Chris
  2. Upgrading is a huge problem for users of Mac and Linux, since VIPM hasn't been updated on those platforms since 2014. Jim, can you confirm that VIPM support for Mac and Linux has been abandoned? It would be good to know whether I should find an alternative to VIPM.
  3. I think you're misunderstanding what I'm saying. The problem here is that Mac and Linux cannot be used to install packages built with VIPM 2017. I'm not talking about earlier versions. You mention that having the source and build spec would allow someone to use a package on Mac or Linux, but that doesn't help at all in the most common case where only the .vip file is made available. As far as I know, all the packages on LabVIEW Tools Network, JKI Package Network, etc do not have source files and build spec available for download. This means that future builds of released packages made with VIPM 2017 will not be available on Mac or Linux.
  4. From the VIPM 2017 release notes: The only solution to this is to upgrade to VIPM 2017 if you want to install any packages built in that version. The problem here is that VIPM 2017 does not exist for Mac or Linux. In fact, version 2014 is the latest available download for those platforms. This means that any new package built with Windows cannot be installed on any non-Windows systems, effectively eliminating VIPM support for Mac and Linux. If you use VIPM on Mac or Linux, you may want to hold off on upgrading to LabVIEW 2017 until this gets resolved.
  5. Thanks, hoooovahh. That's good to know it's possible to download VIPM 2017. However, it looks like the Mac and Linux downloads are still at 2014. This means I won't be able to build VI packages using VIPM 2017 if I need to distribute them to Linux computers, which is a big problem for me. It would be great if someone from JKI could address this.
  6. It looks like VIPM 2017 is included with LabVIEW 2017, but it is not yet available for download on https://vipm.jki.net/download. This would normally be fine, except I noticed in the release notes that packages built with VIPM 2017 cannot be installed with older versions. This is a potential problem because anybody who has installed LabVIEW 2017 cannot currently distribute their newly built packages to people who are still using older versions of LabVIEW, since they have no way of getting their hands on VIPM 2017. Also, can anyone confirm that there will be Mac and Linux versions of VIPM 2017? If not, that will be a big problem for those of us who build packages on Windows then need to install them on other OSs.
  7. It appears that VIPM 2014 packages are not backwards compatible. If you build a package using 2014, opening it with 2013 shows an error saying "This package is not compatible with any LabVIEW version on this computer". This happens, regardless of the LabVIEW versions involved. This seems like it could be a pretty serious problem. If I publish a package using VIPM 2014, I now have to make sure any potential users of that package have upgraded to the latest VIPM, even if they are using an older version of LabVIEW.
  8. This must have been reported before, but I haven't seen any other posts on it. If I click on the "Create new palette set" button, then click "Cancel", the palette icons revert back to the ugly defaults, and the items inside the palettes are wiped out. This can be really annoying when it happens right after I painstakingly set up a palette hierarchy and icons.
  • Create New...

Important Information

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