Patrick Irvin
-
Posts
71 -
Joined
-
Last visited
-
Days Won
13
Posts posted by Patrick Irvin
-
-
@Jim Kring That's an excellent suggestion. I think most of that icon is transparent. I will try that
-
1
-
-
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
-
1
-
-
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
-
1
-
-
-
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)
-
1
-
-
I can't resize to find the yes or no buttons:
-
1
-
-
@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
-
1
-
-
It's not a showstopper, but I would say somewhat yes. Looking at the following screenshot, what it is the quickest way to switch back to my project?
Also seeing the icon highlighted let's me know that LabVIEW hasn't crashed when I wasn't looking 😅 But I will say that I have not used it in this mode extensively yet, so maybe it is something to get used to. Maybe adding a Dragon icon to the taskbar will help?
-
1
-
-
Yes, exactly - just make it more convenient to switch back and forth, and keep the focus on Dragon when in LabVIEW. (and encourage team members to interact with VCS often.)
My workflow in GitHub Desktop is to do the most common actions like commit/push/pull and basic branch switch/merge. And then I go to the website to handle releases, edit issues, edit readme files. (Other more advanced actions like checking out an old commit needs to be done via the command line or something like TortoiseGit or Git GUI.)
-
1
-
-
1. Project is embedded in Dragon Window. Help>> About shows that LabVIEW is running.
2. LabVIEW does not appear to be running based on Task Bar icon
I don't know if this is expected behavior, but it feels...weird:
-
2
-
-
@Jim Kring great idea. I agree that it might not always be necessary to go into the VIPM main window, but it's just what I'm used to!
-
1
-
-
HI @Jim Kring,
I interact a lot with GitHub using GitHub Desktop (and switch back and forth with LabVIEW a lot). I'm thinking that adding a shortcut to the Dragon sidebar that will take you to a VCS will help to keep Dragon at the center of all of the action. Hopefully this screenshot comes through:
-
1
-
-
Hovering over the Dragon icon shows "Search for LabVIEW Tools..." but it should say something like "Open Dragon...":
-
Idea: add (user-configurable) shortcut to source code control:
-
1
-
-
Clicking the Dragon button opens the welcome screen. Then the user needs to click "Open VIPM" to open the VIPM window.
Idea: add a shortcut directly to VIPM:
-
1
-
-
Double clicking a .Dragon file only opens the Dragon welcome screen. The behavior I was expecting is to open the LV project file
-
1
-
-
Clicking the *.lvproj file opens the normal project window in LabVIEW, not in the Dragon wrapper. The result is that even if .dragon specifies a particular version of LabVIEW a developer can unwittingly open the project in the wrong LabVIEW version.
Idea: change this behavior such that Dragon handles opening the lvproj file (in the proper LV version).
Bonus idea: "Developer A" can require that Dragon be installed and used to open the lvproj file (further protecting us from accidentally fast forwarding the LV version)
Caveat: What if we mean to open in the "wrong" LabVIEW version?
-
2
-
Missing Function Palette Icon
in VI Package Manager (VIPM)
Posted
yeah!! super helpful thank you