Patrick Irvin

yeah!! super helpful thank you

@Jim Kring That's an excellent suggestion. I think most of that icon is transparent. I will try that

PS I'm using VIPM 2020.3

I'm having some difficulty with missing palette icon. Here it is configured in the Package Builder: But when I install the package the palette icon is blank: As you can see many of my other palette icons work. Any tips for diagnosing this problem? Thanks

I noticed that packages installed into lv-env also have their help and examples installed in the same directory, rather than the global director. This has ramifications for using "search for example" menu item. It may also impact help and other menu items.

Hi @Jim Kring yes, it was no problem with the main UI. thanks

Trying out Dragon with JKI SMO project: 1. Try install all required dependences in Dragon. Stuck on "resolving dependences" for hours 2. Try install packages 1 at a time. JKI State Machine 3.0 and jki_rsc_toolkit_palette OK. Would not install three dependencies (from Dragon window) 3. Open vipc file and was able to installed the remaining three packages into lv-venv (they are all unpublished and exist only inside the vipc file)

I can't resize to find the yes or no buttons:

@Jim Kring Yes clicking the .dragon file now opens my project in the Dragon window. - I saw some strange behavior the first time - I did not see any splash screens indicating anything was happening until my project showed up in the Dragon window. Subsequently I see the splash screens of VIPM and then LabVIEW. - The project I tried takes about 4 minutes to load, including 1 minute for VIPM to start, which is before LabVIEW opens. I'm not sure if the time is due to number of files, number of dependencies, reliance on global packages, etc...

@Jim Kringyes working now. I see "Open Welcome Window"

Hi @Jim Kring yes that did the trick to remove and then add. See below for more thoughts:

The JKI State Machine Explorer is amazing and incredibly helpful. One deficiency I've found is that browsing through the (potentially long) sequence of states found in a Macro can be somewhat cumbersome. An improvement idea I have to is to somehow represent the potentially long sequence of states in a macro in a sidebar or separate window. Mock-up shown below:

Hi @Jim Kring, This morning I came across this issue with updating the VIPC contents. I'm not sure if it belongs in this issue or not, but I'll post it here for now:

Yes I also use alt-tab a lot, and that is the correct answer to "quickest way", but alt-tab doesn't help me prove my point