Jump to content

Antoine Chalons

Members
  • Posts

    4
  • Joined

  • Last visited

  • Days Won

    2

Antoine Chalons last won the day on October 11 2023

Antoine Chalons had the most liked content!

Recent Profile Visitors

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

Antoine Chalons's Achievements

Rookie

Rookie (2/14)

  • Reacting Well Rare
  • One Year In
  • First Post Rare
  • Week One Done
  • One Month Later

Recent Badges

4

Reputation

  1. This feature request would be a work-around to the bug reported here. If VIPM API had a VI the returns the package list as an array of string then I wouldn't have to use OpenG ZIP Tools to get the file list inside of the VIPC Of course an alternative would be to use LabVIEW's ZIP VIs but they're much more basic and slower, and they'd require to actually extract the zip, to then list the files, which is not what I want, the OpenG ZIP Tools allows to get the file list without actually decompressing the IP.
  2. VIPM API comes with an internal copy of the OpenG ZIP Tools package, that creates an issue if in the same VI/project we use VIPM API and a VI from OpenG ZIP Tools VIPM API's internal OpenG ZIP Tools uses the library : C:\Program Files (x86)\National Instruments\LabVIEW 2020\vi.lib\JKI\_VIPM API_internal_deps\lvzlib.* Whereas OpenG ZIP Tools uses the library : C:\Program Files (x86)\National Instruments\LabVIEW 2020\user.lib\_OpenG.lib\lvzip\lvzlib.* And LabVIEW doesn't like that... Wouldn't be simplerto set OpenG ZIP Tools as a normal dependency package of VIPM API package?
  3. For most our customers we deploy our LabVIEW built applications on Linux Desktop (Ubuntu) We have a CI server on GitLab, so it would really help us to be able to use VIPM API on Linux. Cheers
  4. Hello I have a large package that contains about 700 VIs (many classes with a large inheritance tree) and very often when I build it, I get an error 1055 on some VI, not always the same one. When this happens, I have to take the following steps : - close LabVIEW 2019 SP1 - close VIPM 2020.3 (build 2540) - delete the VI Object Cache - go to ProgramData\JKI\VIPM\Cache and delete the Spec Database Datalog.sdd file Spec Datalog Summary.sds (don't ask me how long it took me before I tried that the first time) - reopen LabVIEW and VIPM as admin - then the build process has a chance to go through. Any idea what the issue could be?
×
×
  • Create New...

Important Information

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