Jim Kring

Hi there. Thanks for your question. Yes, VIPM users need Pro to subscribe to a custom repository.

Right, we don't have a build of VIPM for Catalina yet...

Hi James. Thanks for posting this -- it's sure to be super helpful to VIPM users on Linux. Ya, there are lots of little gotchas like this that pop up on various Linux flavors, and it's nice to have a record of what worked for others (or myself, when I find an old post of mine answering the question I'm now asking!). -Jim

Hi Greg. The buttons' Boolean Text is 20 pt Application Font, so it depends on the font you've got configured on your system. The control labels and captions are set to 15 pt Calibri -Jim

What icons do you think would work well for write and read? In your application, what is it that you're trying to Read/Write and Send/Receive? That might help us find some good icons for your use case. By the way, there is an "Edit" button with a Pencil. For reading, would expect glasses? PS - Sorry for the crashes. we're not sure why LabVIEW has a difficult time, sometimes 🙂

Hi Eldon. The context menu items only show up in LabVIEW 2015 and greater, since that's the first version of LabVIEW that supports this ability to create plug-ins for the context menu. You should be able to use quickdrop to open the JKI SM Explorer window via Ctrl+Space >> Ctrl+J.

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?

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)! 🙂

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...

Do you already have LabVIEW installed? You could try installing the LabVIEW 2015 Runtime Engine before installing VIPM, to see if that helps.

Hi @DavidLee1997 thanks for testing and for letting us know what you learn over in the NI forums. Linux can be tricky, for sure.

Hi David. I don't any ideas about how to get around that. Have you tried posting to the LabVIEW Linux Users group?

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.

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.

Hi Greg. I think I’m using Tahoma

There’s an obscure control setting that allows one to configure the icon parts to not stretch when the control is resized.

Here's how the control you uploaded looks on my system -- it's 2px below the midline.

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.

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?

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?

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)!

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.

Hi Sebastian. You're welcome, thanks for letting me know, and wishing you the best of luck on the project.

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.

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