[VIPM 2020 redesign needs some care and attention]

A recent conversation on LAVA: https://lavag.org/topic/21631-anybody-having-problems-with-vipm-2020-and-how-can-i-get-vipm-2019/?tab=comments#comment-132642

Suggest multiple LabVIEW developers are unhappy with the 2020 version of VIPM.  I think you have been a bit aggressive in the number of changes, and you need to quickly get on top of some of the issues.  You need a 2020.1 version soon.

[VIPM 2020: No main window after splash screen on Windows 7]

How can I find a copy of VIPM 2019?

[VIPM 2020: No main window after splash screen on Windows 7]

VIPM 2020 running in task manager, but main window does not appear, nor is VIPM icon in windows tray (Windows 7 on a Parallels virtual machine on a MacBook).  Can open build specs and get that window, but cannot install packages.  

Attached is image of Build Spec window , but no main window.

[VI Calling VIM Fails to Build [fixed in VIPM 2017f1]]

Interestingly, I have a couple of VIMs that contain other VIMs, and they don't produce this error. Only the VIs that call VIMs do.

[VI Calling VIM Fails to Build [fixed in VIPM 2017f1]]

I have the exact same issue:

 

 

At the moment, I'm only calling VIMs inside my Examples, and so I'm excluding Examples from the package temporarily.

[Processing events in JKI state machine]

Note that if you do this you are committed to making sure that any sequence of “states” you call must be able to handle any possible external interruption at any point. In other words, you must be super vigilant against race conditions. With the “idle” method, one can choose where in a sequence of steps one will accept outside input.

 

For example, if you had the macro:

 

Take Data

Analysis Data

Save Analysis

 

and also a “Set Parameter” event that changes a parameter used in Analysis and Save, then you have a race condition where the analysis may be saved with a different parameter value, if the “Set Parameter” happens between Analysis and Save.