Jump to content

Antoine Chalons

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

10 Good
  1. Great job, thanks for dealing with this so fast! And indeed, this kind of issue makes you wander what else you haven't seen ye
  2. I guess a fix would be to use the one from LabVIEW in EasyXML, no? I've just uninstalled - reinstalled the OpenG String package and the bug has not come back. Haven't connected to my Linux RT target though. EDIT : my VIPM is set to mass compile packages after install (has always been configured like that)
  3. Nope, never on a mac but this project can be run either on Windows or on a NI Linux RT target, so I naviguate between Linux RT and Windows almost every day. Will try that.
  4. I had LV 2019 SP1 and then I installed LV 2020 SP1 Never installed 2020.0.0 Sorry for the lack of accuracy.
  5. [ Update: The work-around for this issue is to OpenG String v4.1.1.16 ] Take a look at this "issue" that can appear after installing LV2020 : https://lavag.org/topic/21753-1d-array-to-string-not-compiling-correctly/ The video posted shows how to fix it. What happened to me was : - I've been using EasyXML happily for some time in LV2019 (my use include attributes) - I installed LV2020 - EasyXML in LV 2019 started to add an extra line at the end of attributes. I noticed that in Git when my config files had so many modifications. - for a few days, it's be
  6. I manage about 20 internal packages for my company and some of my package are "low level", I mean used by other packages. OpenG packages do that too. It would be cool if VIPM could produce a view similar to the VI hierarchy but for package.
  7. What files should I send you? The content of C:\ProgramData\JKI\VIPM\cache or C:\ProgramData\JKI\VIPM\databases\LV 19.0 or both?
  8. As you can see below, VIPM is offering to update the OpenG LabVIEW ZIP Library but I already have the latest version (4.0.0-2) Maybe this confusion come from the fact that I have OpenG ZIP Library 4.2.0b1-1
  9. Ok, thanks for this, no less than what I was expecting from JKI 🙂 I don't really use NXG yet, I installed NXG 4.0 and had a quick look around, nothing more for now. Not sure yet when I'll start migrating my customer project, probably around end of 2020. At the moment I'm listing all the NI modules/drivers and "community modules" that I use in CurrentGen and start checking if and when they'll be available in NXG.
  10. 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?
  11. version 2.0.1.24 requires JDP version 1.0.4.93 but the latest available version is 1.0.4.92 See image :
  12. Use case : When working / debugging on a PreBuild or PostBuild action VI, I sometime keep the Pre/Post Build VI' FP & BD open for debugging in the context in which it was opened by LabVIEW when the build was started (NI.LV.MxLvProvider context instead of the usual main application context that you can see at the bottom left corner of the VI windows). When I am in this context, if I open the JDP, try to drag a control onto the front panel of the VI that is in the NI.LV.MxLvProvider context it doesn't work The work-around is to drag the control into another VI in the main app
×
×
  • Create New...

Important Information

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