Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 06/03/2020 in Posts

  1. 2 points
    I do not know what I am doing wrong: I have an account on https://www.vipm.io/ where I can log in. I have VIPM installed and it was just recently automatically updated. I am able to install i2 JSON for 2018-64 I am not able to log in for "community" or "free" status. When I choose in the new window "Use existing JKI account" I get an error message, when using the account data for www.vipm.io. I also get an error when choosing "Sing up for a new JKI account". When pressing "Forgot your password?" an new tab in the browser opens where I can write my mail address and it tells me that an email was sent. However, I nether get the mail, nor is it gone to my spam folder. What can I do to solve this. I rely in my largest project on the OpenG lib and the MGI lib, which was not a problem to install in previous time. Best regards Wolfgang Kilian
  2. 2 points
    Some advanced users are asking for support to install VIPM for Windows onto a Docker container. This would allow creating fully automated build processes that spin up virtual machines that have LabVIEW and VIPM installed on them, so that VI Packages can be created automatically.
  3. 1 point
    Similar issue, im not able to activate this via email. I send out the email request and never receive an Activation code. Is there an alternate method of activation available? Fixed now, looks like my account was not setup to receive emails from JKI
  4. 1 point
    Hi Everyone @Mads Toppe, @szymsciupak, @wolfkil, This is a known issue that affects some people behind corporate firewalls. In VIPM 2020.1 (still in beta), you will be able to download packages without a sign-in and hopefully this will resolve the pain point. Thanks for your patience. -Jim
  5. 1 point
    Hi Thomas, Actually, we use some 32-bit shared libraries, including OS libraries and also some 3rd party libraries, like the OpenG Zip Tools. For the MacOS beta, VIPM migrated to using command line zip/unzip tools and dropped a couple minor usability features that maybe nobody will notice (like extracting lvlib/lvclass icons from the XML file, which requires zlib deflation). However, for MacOS, we figured it was better to have things mostly working OK in 64-bit than not at all. For Windows, we wouldn't want to lose any functionality. I hear you about the memory limit issue. I hope that's helpful information, and please know we're not hesitating to explore 64-bit, for no good reasons. Regards, -Jim
  6. 1 point
    Always forward, Jim I don't want to bring up the "increased performance" argument. I mean, we're using LabVIEW after all. Nobody who's using LabVIEW can seriously play the performance card. I regularly see VIPM using over 1GB of memory and sometimes crashing with an "out of memory" error - although that might be due to the ridiculous 4GB of total memory available on that machine. How long before that goes to 2GB, 3GB? We've had 64bit on windows for 15 years now. I think it's time to move on. At least give us the option. Surely VIPM isn't depending on modules that don't exist in 64bit land
  7. 1 point
    I am having trouble installing VIPackage Manager 2020. I keep getting the following error: Any help would be appreciated.
  8. 1 point
    It would also be nice to have the shell menu option "Add to VIPM Library." on *.vip files and not only on *.vipc files. This way *.vip files can be added to the VIPM library from the windows explorer without having to install them.
  9. 1 point
    I have the same problem now, irritating as hell. Having paying customers is of course the optimal for JKI, but it still seems silly to chase everyone over to alternative solutions. It is the adoption rate after all that makes the platform interesting for package publishers. And now that we are all forced to register to download even the open source projects proper logon functionality has become critical. Please support every user, and fix the connection issues.
  10. 1 point
    Alin, Thanks for the detailed description of the bug. It helped me to reproduce it. I have recorded this issue as Case 18752 for consideration. I can't promise when this will be fixed but we will inform you when that happens. Since JKI State Machine Editor is open source, you can post any issues in GitHub: https://github.com/JKISoftware/JKI-State-Machine-Editor/issues Take care and stay safe.
  11. 1 point
    Hello, I have exactly the same problem. When trying to sign in or create new account, I get the message as in the screenshot attached.
  12. 1 point
    In installing the JKI Flat UI Controls with LabVIEW 2020 on Mac OS, the package claims requirement to install JKI Design Palette. However this Package is not listed as available on the Mac. Not sure if there is something fundamentally not allowed on the Mac OS or if it was an oversight in packaging the JKI Design Palette. Furthermore, VIPM reports that there is also a missing dependency on OpenG Port IO which is a very old package that has never been compatible with the Mac OS. And is not part of most windows machines that haven't had a "Printer Port" in years. However that is a dependency in the OpenG toolkit which I use despite that missing dependency. However it now blocks in stallion of the JKI Flat UI Controls. (Note I believe that this issue is also in earlier versions of LabVIEW (does not work in LV 2019) as well, I just decided to update my controls UI using a modern looking set with a change to 2020)
  13. 1 point
    I don't see the way to "ignore dependency". Still looking through help.
  14. 1 point
    Is this going to be in the next VIPM version?
×
×
  • Create New...

Important Information

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