Jump to content

Jim Kring

JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts 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. On 9/26/2019 at 7:00 PM, DavidLee1997 said:

    Having followed all of the above suggestions, I am still unable to open VIPM.  When I run the command "sudo ./vipm" I get an error "Unable to open X display".  I am using openSUSE 15.1, and trying to use VIPM 2017 with LabVIEW 2017.

    Any suggestions on how to run this one down?

    Thank you!

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

    • Like 1

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

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

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

    1. False Color
    2. True Color
    3. False to True Color
    4. True to False Color
    5. Hover While False
    6. Hover While True

    Depending on how you're using the button, you'll want to set these colorings appropriately.

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


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



    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.

  • Create New...

Important Information

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