Jump to content

Jim Kring

JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Jim Kring

  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)!
  15. Go figure... Another thing to note is that Windows has some sticky keys (another other) tools that intercept keystrokes and so who know what might be going on under the hood at times. I'm glad it's working for you, now.
  16. Hi Sebastian. You're welcome, thanks for letting me know, and wishing you the best of luck on the project.
  17. Hi Ian. Thanks for reporting this. We've had some users communicate issues with the keyboard shortcuts when using LabVIEW inside of a Virtual Machine. Would that be the case for you? Can you let me know a little more about your system setup (Virtual Machine? Windows version, LabVIEW Version, JKI Design Palette version)? Thanks.
  18. Hi Kellen, There are a couple good solutions: VI Package Configuration files and VI Package Repositories. Yes, installing packages, will install the required VI's beneath the LabVIEW folder -- that's sort of how LabVIEW works, and it's definitely a pain for many users, especially when IT has to be involved 🙂 There's a good article on using packages in your project, here. -Jim
  19. Hi @Ruslan. A you're noticing, changing the colors so that they look good is a little bit tricky. There is a Boolean Control property you can write to called "Colors [4]" (which is an array of 6 elements, for buttons with hover effects). The 6 elements are: False Color True Color False to True Color True to False Color Hover While False Hover While True Depending on how you're using the button, you'll want to set these colorings appropriately.
  20. Hi Bob. Error 8 is a file permission error. Please try this: 1) shut down LabVIEW 2) Go into VIPM and install EasyXML 3) Wait for VIPM to start LabVIEW, and then see if EasyXML installed OK If that doesn't work, retry the above steps, but launch VIPM as Administrator -- try it first with VIPM launched normally. Please let me know how that works for you.
  21. That's very interesting and odd. I haven't been able to reproduce this on my end, and I don't know if I've heard anyone else complain about this. I guess it could be due to some dependency. The JKI Design Palette is built into a PPL, so it should be pretty well isolated from such problems. When that happens, can you try opening the design palette manually (using File >> Open) and see if it's broken and if there's any useful information about why it won't run?
  22. Thanks, @kosist! This will be fixed in the next release! I see you found the CTL file. You can modify and save that file, and it should work for you. Here is a fixed file, in case you need it: Boolean--Add-Plus-Transparent-Button-(flat).ctl You can replace the existing/buggy file in the "<LabVIEW 2017>\resource\JKI\Design Palette\Themes\JKI Flat UI 2.0" folder so that this new fixed one will show up in the Design Palette.
  23. I'll follow up with you by email, regarding how to do this.
  24. Hi there. In these cases it's either because the Installation ID had a typo when copied/typed into the web dorm or a different email address was used (or there was a typo). Please double check that, and let us know if it's still not working.
  • Create New...

Important Information

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