Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. Hi Antoine, Yes, we intend to migrate EasyXML to NXG when the time is right. Realistically, that will probably happen sometime in 2020. I don't see any major technical challenges in doing so, yet the type descriptor and flat data parsing may need some improvements due to unicode strings. There aren't too many people actually using NXG yet, but that will start to shift in 2020 with NXG 4.0 and 5.0 beta, from my perspective. Thanks for checking in. Are you using NXG?
  3. I'm in no rush to move project to NXG, but I am curious, I saw on GitHub that JKI is has worked on a JKI State Machine for NXG and I was wondering if there was any similar project for EasyXML. I'm assuming the transition of this toolkit is not going to be a huge problem, am I right? I'm also assuming some NXG early birds have already tried the transition of EasyXML, anyone?
  4. Thanks for sharing this Bob. Hopefully, it turns up in the Google search for anyone else having the same issue. Sometimes when I'm searching for answers on Google, I find posts by me where I've answered (in the past) my own question (in the present)! 🙂
  5. I've been using VIPM for years to access the LabVIEW Tools Network. Recently, one of my machines was set up with a User Account (where I do most of my work) and a separate Admin account. A while ago, I tried to install EasyXML and got a strange error (among other things, I was told the package was not compatible with my OS nor any version of LabVIEW installed on my computer). Turns out the "fix" was to run VIPM from my Admin account. But do I learn? No, months later, I try to install another package. Similar error. While browsing this Forum, I run across my previous note and see "Run VIPM as Administrator", which (are you surprised?) fixes this "new" error. You'd think I would have learned my lesson, but I can at least pass on this warning. Bob Schor
  6. Earlier
  7. Thanks for reporting this. We're still not sure why it's happening, since it's oddly intermittent. We'll keep looking and let us know if you have any more info about the error...
  8. Got same error from time to time. Have to restart LabVIEW. LabVIEW 2019 32bit Windows 7 Pro.
  9. Elias, Glad to know that you were able to resolve the issue. Also, we really appreciate you sending this piece of information.
  10. I missed the part where you are using a VM for this. Are you accesing from a remote X session? If so, the root user will require some additoinal authorization to run GUI based applications in remote sessions.
  11. One of my colleages found a sulution: I had to check the security checkbox under the general properties of the VIPM installer file. After that, the installation was successfull.
  12. Would like to have a flat meter indictator, ideally able to have two needles like the silver version.
  13. I'm using LabView 2018 Professinal Development System on this computer and installed now LabView 2015 Runtime Engine. I also tried the installation with disabled antivir programm. Unfortunately there is no difference.
  14. Do you already have LabVIEW installed? You could try installing the LabVIEW 2015 Runtime Engine before installing VIPM, to see if that helps.
  15. Not sure what is going on. Might be related to network. If this option does not work, you can always get latest and greatest version of VIPM from: https://vipm.jki.net/get
  16. Elias, Try to run the installer with "Run As Administrator" option that you get on RighMouseClick or Shift+RightMouseClick.
  17. Hi I would like to install VIPM 2019 on my Windows 10 Enterprise PC as an local administrator. After I accept the Licence Agreement in the setup wizard, select the installation folder and define the desktop icon, the installation window freezes and nothing happens anymore. I can only quit the installation by the task manager... Any ideas wich can help? Thx Elias
  18. Hi @DavidLee1997 thanks for testing and for letting us know what you learn over in the NI forums. Linux can be tricky, for sure.
  19. First, I confirmed that the CentOS VM is using Xorg. Using the openSUSE VM, I confirmed that the default x server is Xorg (echo $XDG_SESSION_TYPE responds with x11). I was unable to launch VIPM (unable to open x display). Changing over to Wayland, I again received the same error message. I will be posting this update over in the NI forums, in the Linux Users group. Again, if anyone has suggestions, I would appreciate them.
  20. All- Thank you for your responses. I will post the question on the NI LabVIEW Linux Users group, and I will also verify the X server that I am using, changing to Xorg if necessary. I will post the updates here and in the NI user group. On a side note, I switched the VM over to CentOS7, and I have been able to install and run VIPM using the above link to the additional packages.
  21. This may be due to the Wayland X server. If you are using Wayland, try switching to the Xorg X server and see if the command works.
  22. Hi David. I don't any ideas about how to get around that. Have you tried posting to the LabVIEW Linux Users group?
  23. Hey Sam. This should be fixed in VIPM 2020. If you're interested in helping beta test it, please sign up for the LabVIEW 2020 beta.
  24. Hi Sam. Thanks for reporting this. Yes, I'm guessing you're right that it's an issue with the *.vim file extension. I'll have our team look into it.
  25. I have a library with some VIMs and regular VIs. On the Display information Screen in the package builder I have Edit All VI Descriptions checked. My regular VIs get the copyright notice added, no problem. The VIMs don't. I am using VIPM PRO 2019.0.0.0. Checked for an update. It says I have the latest. Source Code is in LV19.0f2 if that helps. I suspect the vim file extension may be causing the issue. I attached a simple reproduction. thanks for creating such a great product! Sam VIM Descr Issue.zip
  1. Load more activity
×
×
  • Create New...

Important Information

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