kosist

Hello @Jim Kring hope you are doing fine. I'm just curious, whether you are planning to continue with Dragon development/releases, or there are some issues, so release is not possible at the moment? Thanks in advance.

What exact version/build of VIPM 2020 do you use? I've tried it just right now (with version 2020.3, build 2540), and everything works like a charm. Login is OK, and also I could request password reset - e-mail was sent immediately. By the way, did you check spam/junk folder of your e-mail inbox? That reset password e-mail could go there.

Hello Jim, great, thanks a lot!

That would solve the issues of installing project providers, quick drops, etc. into local environment... But also it would be nice to set somehow such option without package rebuild (in order to update existing packages available online) - maybe it could be possible to set it via vipm.io. VIPM downloads packages from repository, so it could check permissions which are set for the particular package directly in the repository...

Thank you, seems that it is fixed. Now when VIPC path is changed to wrong one, toolkits are anyway shown - just they are shown as not included into VIPC.

Thank you, now it asks and if confirm deletes installed packages. But it is strange that dialog window in my case is shown in upper left corner of the monitor (I'd expect it to be shown as on your screenshot, in the middle of the Dragon project window):

Thank you, now it opens Dragon window when VIPM is opened.

UPDATE: don't know how to reproduce it yet, but here is approximately what has happened. 1. Opened one project in Dragon. 2. Then created new project in LabVIEW, left it opened. 3. Created new Dragon project with LV project created in step 2. 4. Installed there toolkit, just for testing. 5. Closed both Dragon projects, so Dragon was closed completely. 6. LabVIEW icon remained in task bar. 7. When clicked on it - the following window was shown: So this is 2nd project's window, but without title of the window.

Thank you, now SQLite library was installed without errors.

Thank you, now it detects version of LabVIEW empty project correctly.

Issue is still present. But now menu could be called not on all empty space, but right after the last project in the list: And then again -> selected Open -> Cancel -> empty window was opened.

Thank you, looks like the issue is not reproducible anymore.

1. Created LV project, added empty VI. 2. Created new Dragon project, selected above created project. 3. Opened Resources tab, Add Package -> SQLite Library in lv-venv folder. 4. Started installation. 5. Installation gets stuck on "Reading VI Linker" operation. But, toolkits are shown as Installed in VIPM window. 6. Pressed button "Cancel" in small VIPM Handler window -> window was simply closed. 7. Pressed red round "Abort current operation" button in VIPM window -> button disappeared. 8. Closed Dragon window -> it was simply closed, but VIPM remained opened. 9. Had to kill VIPM process via Task Manager. 10. Reopened Dragon project again, and opened VI in the project. 11. Checked functions menu palette. SQLite menu entry is there, but no VIs are loaded: 12. Inspected lv-venv folder on the disk -> VIs are present on the disk. 13. Tested this behavior in LabVIEW 2020 and LabVIEW 2017 - result is the same. 14. Tried to install SQLite Library into global environment via Dragon -> everything works fine. 15. Tried to install some another toolkit locally (OpenG Boolean library) - everything works fine. Maybe, it is issue just of SQLite Library toolkit, but for sure there is something not OK overall - somehow VIPM gets into the state when it is not responsive, and one has to kill it via Task Manager.

1. Created empty LabVIEW project (so just project, without any VIs) in LabVIEW 2020 (tested also with LV 2017). 2. Created new Dragon project with above created LV project. 3. Dragon shows project's LV version as 2013. LV 2013 - is the lowest LV version on my PC. When new project is created, and there is added at least some VI - then version is detected properly. UPDATE: it detects version properly when VI is in the project's folder. When project contains VI which is stored in another folder (outside of the project's folder), then still version is not detected properly.

VIPM is opened. Then double-click on Dragon shortcut on Desktop (this shortcut is created during installation). Dragon's icon is shown for a while in task bar, and then disappears. No Dragon window is opened. So then the only way to launch Dragon is to click on Dragon icon in VIPM window...

Deleting lv-venv folder sounds fine, thank you. But, then Dragon should "remember" which packages were used, so user has to install them globally. Based on this thread https://forums.vipm.io/topic/3670-display-list-of-missing-required-packages/ as per now Dragon "cares" just about packages installed locally, isn't it? It would be nice then to keep configuration from project's point of view: what packages are installed, and in which environments (global or local). So if user decides to delete lv-venv, Dragon will "switch" configuration to global, so on open project on another PC proper packages will be installed at the proper place.

1. Create Dragon project, configure it to install packages under Dragon project folder. 2. Install some packages. 3. Use VIs from the packages in the project. 4. Then, deselect "Install Packages Under Dragon Project Folder" checkbox for the Dragon project, save changes. 5. Close Dragon project. 6. Open Dragon project. 7. Open LV project's VI -> there is no functions palette for the locally installed packages. 8. Open Resources tab -> there is no displayed locally installed toolkits. It would be nice when Dragon could handle such situation - for example, anyway display list of locally installed packages, or functions palette. Or, by forcing user to delete local packages and use global packages instead. Also, if such project will be, for example, pulled from repository to another PC, Dragon project will be opened -> it will ask to install missing toolkits -> and it will install them globally. So that will be two different projects already due to different dependencies. I've simulated it by removing lv-venv folder after step 5.

While drag and drop package from global node to lv-venv node in the tree view - this dialog window is shown, regardless whether dropped package is/is not installed in the lv-venv folder. While drag and drop package from lv-venv node to global, and that package is not installed in global environment - then toolkit's installation starts. While drag and drop package from lv-venv node to global, and that package is already installed in global environment - nothing happens. No dialog window is shown. Just, tree view is reset to default position (so scrolled completely up).

I've seen such "artefact" couple of times when somehow Dragon was active, and LabVIEW icon was visible in the tasks panel also (but Dragon's "LabVIEW Project" tab was not active, and no VIs were opened). I couldn't reproduce that particular situation, but in that case LabVIEW project window (menu bar) was visible somehow "outside" Dragon window - it was kind of floating, but it was not possible to close/manipulate it. But, it is possible to reproduce the following: 1. Open existing Dragon project. 2. Expand window to the whole screen. 3. Resources and Configuration tabs have visible project window (menu bar) in the bottom right corner:

Thank you, it looks great - seems that there is displayed all needed information in order to make the decision whether install toolkits or not.

Steps to reproduce: 1. Launch Dragon. 2. Right-click on empty space in the project's list, select Open menu item. 3. When dialog window is opened, click Cancel button. 4. Empty window is displayed. UPDATE: most probably when right-clicked on empty space, no menu should be displayed.

This is again more about warning users rather than functional issue (because consequences of the described steps are logically understandable, just anyway such situation can happen). 1. Created empty LV project, LV 2020. 2. Created new Dragon project, added LV project there. 3. Installed in lv-venv folder JKI State Machine toolkit. 4. Created new empty VI in LV project. 5. Added there JKI State Machine -> tested -> everything is fine, no errors. 6. Decided to install Caraya globally. 7. Opened Resources tab in Dragon project. 8. Right-click on LabVIEW 2020 -> Install a Package -> searched for Caraya. 9. When found -> selected -> Install. 10. Package Action Confirmation window asked that it is going to install: Caraya, JKI State Machine, jki_rsc_toolkits_palette. Confirmed (b/c apparently those are toolkits which are needed for proper Caraya work). 11. Continued with the installation. 12. Installation completed, without the issues. 13. Opened VI in LV project, tried to add Caraya function Assert.vi -> warning window appeared. Because, Caraya internally uses JKI State Machine toolkit, which is also installed locally now. Solution is to remove JKI State Machine from local lv-venv folder, and leave it to be installed globally. Because logically, it does not make sense to have it installed just locally while using it in other projects. But, similar situation could be with another toolkits which depend on each other (like OpenG toolkits, or MGI toolkits, etc.). I believe that it is developer's responsibility to separate scope of packages properly, but if Dragon could warn user somehow about such issues before toolkits are installed (by analyzing dependencies, etc.), then it would be great.

There are many packages which either are completely done as project providers, quick-drop plugins, shortcut menu plugins, etc. or partially provide such functionality. JKI State Machine is great example of that. It is available from LV functions palette, and also has State Machine Editor functionality (which is mostly shortcut menu plugin). But when JKI State Machine is installed just in lv-venv folder, then State Machine Editor does not work. Similar situation is for other toolkits also - for example, RAFA Language Support Toolkit, ANV toolkits, JKI VI Tester, etc. - there are project providers + functions palette. On one hand, it is developer's responsibility to wisely separate scope of the toolkits installed in the system. But on the other hand, for sure someone could forget about such behavior, and then could face some troubles with figuring out what is actually happening. It would be nice somehow handle it via Dragon. For example, maintain list of toolkits not recommended to be installed in lv-venv folder. Such list could be created on vipm.io, and then Dragon will use it in order to verify toolkits to be installed locally. Also, VIPM package build configurator could have additional flag to indicate whether toolkit could be safely installed in lv-venv, or it should be installed just globally. So toolkits built with newer VIPM version will have that flag set. But the question is what to do with existing toolkits, because not all of them will be rebuilt anyway. Another way - Dragon could determine, whether toolkit has some files which are going to be copied into project provider/popup menu/etc. folders. If so, then we could assume that toolkit has project provider, shortcut menu plugin etc. functionality - so it is not recommended to install it locally. Partial solution (but not sure that it is possible to implement) in order to make shortcut menu plugins working is to provide some hook via Dragon, which will allow to load plugins from local lv-venv folder. But for sure, there could be some more elegant solution which will allow at least to warn user about possible consequences while installing such kinds of toolkits locally (in lv-venv) folder...

Hello @Jim Kring, sorry for the confusing description, let me describe steps below. 1. Created new Dragon project, added there existing LV project. 2. Scanned project for dependencies -> created VIPC file with the packages, which are used by LV project. ESF is one of them. 3. Uninstalled all those packages globally. 4. Each uninstalled packaged was automatically moved under "Virtual Environment" node in Resources view. 5. Right-clicked on the toolkit under that "Virtual Environment" node -> Install Package -> in case of ESF toolkit error was shown and toolkit has not been installed. 6. Open VIPM window, it had active selector set to project name. 7. Located ESF toolkit in VIPM window. 8. Tried to install -> installation has failed. 9. In VIPM window, removed project selector (so LabVIEW versions were displayed). Located ESF toolkit -> installed it (globally) -> installation was OK. 10. Uninstalled ESF. 11. Tried to repeat steps 5 - 8; result was the same. 12. Closed Dragon project, opened it again -> it asked to install missing packages. After confirmation, ESF was installed under lv-venv folder.

UPDATE: after Dragon project was closed and opened again - it asked to installed missing dependencies. And it has installed ESF toolkit locally in lv-vevn folder without errors.