Jump to content

Jim Kring

JKI Team
  • Content Count

    1,498
  • Joined

  • Last visited

  • Days Won

    28

Jim Kring last won the day on October 7

Jim Kring had the most liked content!

Community Reputation

44 Excellent

4 Followers

About Jim Kring

Recent Profile Visitors

25,919 profile views
  1. 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?
  2. 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)! 🙂
  3. 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...
  4. Do you already have LabVIEW installed? You could try installing the LabVIEW 2015 Runtime Engine before installing VIPM, to see if that helps.
  5. Hi @DavidLee1997 thanks for testing and for letting us know what you learn over in the NI forums. Linux can be tricky, for sure.
  6. Hi David. I don't any ideas about how to get around that. Have you tried posting to the LabVIEW Linux Users group?
  7. 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.
  8. 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.
  9. There’s an obscure control setting that allows one to configure the icon parts to not stretch when the control is resized.
  10. Here's how the control you uploaded looks on my system -- it's 2px below the midline.
  11. I think the issue *may* be the Application Font that's configured in LabVIEW/Windows on your computer -- I'd be curious to know more about that. Here's how the numeric controls look on my system.
  12. Hi Greg. Thanks for posting this. We are aware of this, and the only work-around we have found is to adjust the position of the display text down one pixel, relative to the other parts of the numeric control. Unfortunately, that changes the position of the text relative to the background and it looks (very slightly) misaligned (it looks 1px too low). LabVIEW doesn’t provide much possibility for adjusting the behavior of the string text (like making the background transparent when it has the cursor for text input by user. If you discover anything or have ideas about how to fix/improve this, please let us know. does that explanation make sense?
  13. Hi Kosist. That sounds very odd. Somehow the "JKI Design Pallete.vi" instance that's running in the editor context (VI Server Application instance) is broken. I'm not sure how or why that would happen. Thanks for posting the dump file. It sounds like the LabVIEW crash means that something odd is happening under the hood of LabVIEW. Does this only happen in LabVIEW 2017? Have you tried in 2018?
  14. Yes, you can have Jenkins run a set of tests for each commit. You might want to try using the G-CLI tool to run a set of VI Tester tests from the command line. It was created by @jamesmc86 and it's a great tool (we even use it in the build process for JKI Design Palette)!
×
×
  • Create New...

Important Information

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