Jump to content

Jim Kring

JKI Team
  • Posts

    2,021
  • Joined

  • Last visited

  • Days Won

    76

Everything posted by Jim Kring

  1. 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.
  2. 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.
  3. There’s an obscure control setting that allows one to configure the icon parts to not stretch when the control is resized.
  4. Here's how the control you uploaded looks on my system -- it's 2px below the midline.
  5. 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.
  6. 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?
  7. 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?
  8. 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)!
  9. 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.
  10. Hi Sebastian. You're welcome, thanks for letting me know, and wishing you the best of luck on the project.
  11. 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.
  12. 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
  13. 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.
  14. 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.
  15. 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?
  16. 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.
  17. I'll follow up with you by email, regarding how to do this.
  18. 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.
  19. I just checked and it looks like there's one digit missing in your Installation ID data. I'm trying to figure that out, and have sent you an email to try to resolve it. Please reply to that email.
  20. Hi Sebastian. I'm pretty sure the only way to change this is by tweaking the menu color settings in Windows. So, if your customer is willing to do that for all Windows applications, then that could be a good solution. There are some other LabVIEW users who have discussed this here: https://forums.ni.com/t5/LabVIEW/ring-selection-label-appearance-customization/m-p/3259968#M950846 I wish I had a better solution for you. Maybe someone else can think of one.
  21. Hi @kosist Thanks for reporting this issue. Here is a fixed version you can download: Boolean--Settings-Configure-Options-Gear-Cog-Button-(flat).ctl We will include this fixed file in the next release. In the meantime, 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.
  22. Hi @Alfredo_Figueroa. Yes, you can programmatically set the Colors[4] property, which is an array of 6 elements. The last two elements are the hover colors for the TRUE and FALSE states (or maybe vice versa -- can't recall order off the top of my head).
  23. Great. Glad you found a workaround that suits your needs.
  24. Hi Roger, When you purchase VIPM Pro, it is a perpetual license. VIPM 2018 Pro will work with LabVIEW 2018 forever. However, if you purchase an upgrade to LabVIEW 2019 from NI, then you'll also need to purchase an upgrade to VIPM 2019 Pro. It sounds like that feels unfair to you, and I'm sorry. As I mentioned, on JKI's side, it is investing effort to keep VIPM interoperable with new releases of LabVIEW (and Windows OS), so it seems reasonable to charge for VIPM Pro interoperability with newer releases of LabVIEW. That's the world we live in, now -- things are changing constantly, and software vendors must progress to more of a subscription model, for new releases, to keep everything working correctly. The alternative is to be unprofitable and end of life a product or go out of business, which would be bad for the users who depend on the software. I hope that makes sense and sorry if it still feels unfair. I long for simpler times, too. -Jim
×
×
  • Create New...

Important Information

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