Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Yeah I was able to replicate the issues that you described. Creating and empty array/cluster caused all the controls to disappear on the palette. That is why the existing clusters in the palette contains a dummy "Delete Me" control :). You can do the same with a decoration to add it to the palette: AA
  3. Today
  4. In the next release of the Flat UI Controls 2.0 we will be adding a VISA Resource control! For those of you who want to get it soon, here it is: Download: IO--VISA-Resource-Name.ctl Note: Place this file in the "<LabVIEW 2017>\resource\JKI\Design Palette\Themes\JKI Flat UI 2.0" folder and it will show up in the Design Palette.
  5. The initial release of Flat UI Controls 2.0 did not have a VISA Resource control. Many users have asked for this.
  6. Wow! What a fantastic post, Nathan! And, your User Interface looks great. I wanted to let you know that we just posted a (better) resizable string that addresses the "two resizable elements" issue.
  7. In the next release of the Flat UI Controls 2.0 we will be making the String Control resizable! For those of you who want to get it soon, here it is: Download: String--Simple-String-Resizeable.ctl Note: Place this file in the "<LabVIEW 2017>\resource\JKI\Design Palette\Themes\JKI Flat UI 2.0" folder and it will show up in the Design Palette. You can delete the "String--Text-Input-Field-*.ctl" files in that same folder, if you don't want those not-so-well-resizable strings to not show up in the Design Palette anymore
  8. The initial release of Flat UI Controls 2.0 did not have a very good resizable string (the background/frame had to be resized separately from the text area). Many users have asked to make this resizable in a better way.
  9. In any validation setting, the tolerances around measured and reported values is critical, and so is tracking the tolerances for any given parameter being measured, with any measurement device or sensor. To automate the calculation of these ranges and limits within our overall application, we must track the specifications of any of these parameters. This used to be done using a peer reviewed excel table, and was loaded into LabVIEW using the Report Generation Toolkit. This had several drawbacks, but that's not the point of this post. The point is that using Excel means that any text becomes free text and if data isn't entered correctly then it can cause issues with parsing. So I created something I call the Specification Manager. It's a small utility that is intended to only be used by validation test case developers to add new specifications to the database of available specifications that can be tested, or to add new hardware for use in the validation tool. I built this tool in about 2-3 days as a way of trying out the JKI Flat UI 2.0 and the Design Palette. Here's the home screen of the tool: Some things that I think make this a nice UI: Dark background (76, 76, 76) and a nice pop of vibrant color, the icon for the tool uses the same two colors to provide consistency All native windows elements are hidden as this tool is very small and simple, there's no need for a toolbar, etc. Our company uses Century Gothic as a common font in many places, so I used that for some of my UI elements (title bar, specifically) System Chiselled Line separating workflow components of the tool. That horizontal line doesn't look like much, but it's a visual separation of the two things you're supposed to do with this tool. 1) select a file path, 2) manipulate the individual .spec files Listbox to store data - I hate working with listboxes, but I think they are the best UI element for storing continuous data. They look way better than any array I've seen when the data is simple. To add a new specification to the library, you press 'add' and get a dialog window that's a sort of wizard: I used the JKI built-in buttons here to give some sort of icon to the various specifications that can be created. I also changed the color scheme of this wizard to 'light' to signal to the user that this is a dialog/configuration type window and not really part of the core functionality of the utility. If this were a project for a wider audience, I would have customized them a bit more, but as-is, I think it's okay. The symbols are kind of meaningless as the library isn't as vast as I'd like it to be. After selecting the type of specification, you enter the name of it: This screen continues to use consistent fonts, and buttons from the previous screen. Pressing 'Continue' gets you to the heart of what this application is intended to do, modify specifications. (*I typed in random data, please don't double check these against the actual specifications of the 6218 - I will not be using this data in production) I used an array of customized clusters containing the JKI Flat UI 2.0 numerics and enums, then used some more of their pre-built buttons at the bottom for continued navigation. I used the same pop of color on the cancel button, mostly for fun, but also as a way of drawing immediate contrast between the other two operations that the buttons provide. That's about it! This is an internal-only tool, but I think that editing specifications using this small purpose-built utility will be easier than us using Excel to do the same thing. Overall impressions of the Flat UI 2.0 library: Pros: good selection of commonly used buttons and controls, consistent theme across numerics, strings, enums, file paths, and buttons - makes a consistent UI easy to build Color customization of buttons is easy, including customization of the hover-state (which I did to the 'X' button on the home screen of the utility) Wishlist: As with any library of icons and UI elements - a wider selection. I had a hard time finding icons for my 'Add Specification' wizard screen and had to reach pretty far Design palette only launches when using the left ctrl+shift buttons, it'd be nice for it to work with either left or right Cons: Working with the String controls and indicators was a little strange. There are actually two resizable elements in a single control, one for the frame/background and one for the actual text field. I had to be careful when resizing the control to make sure that both fields were resized correctly. Also the front panel snapping meant that the border around the text area was easy to lose if the text field itself was resized incorrectly. I will probably continue to use the UI library for the internal only developer tools, but for the main applications that I'm working on there is still heavy customization specific to my company that I will continue to have to do. Thanks for reading - feel free to ask any questions about the design choices or other elements of the UI for this tool.
  10. Hi all, First, thank you JKI for your great tool that makes the design of my UIs so much easier! I successfully added my own themes and controls to the JKI Design Palette but I noticed some controls are not supported. Arrays and clusters with no elements: data structures like arrays and clusters require to have elements to be added to the Palette. Adding arrays or clusters that don't have elements make all the controls in the JKI Design Palette disappear as shown below. In the future, I think it would be great to be able to add our own arrays and clusters that don't have a type to the Palette. Decorations: decorations can't be added to the Palette. I tried to add my own decorations to the Palette and it looks like they are not supported. It didn't make the other controls disappear like above but I think it would be a great improvement to have access to decorations (classic or our own) via the JKI Design Palette. Best, Benoit
  11. Yesterday
  12. We implemented offline activation in version 1.0.1. Please give it a try and let us know how that works for you.
  13. Thanks, Christian! That's very helpful. The issue is that we had the font for that set to Dialog Font and everything else is using Application Font. Hopefully, it'll be fixed/better in the next release. I appreciate you helping us make the Design Palette better and hope it works well for you. I look forward to any other feedback you have, as you take it for a spin on your projects.
  14. Local configuration, FYI: Windows 10 font scaling is at 100% LabVIEW fonts are all defined as "tahoma 13" in ini.
  15. That's to protect privacy... But seriously, thanks for letting us know. Font sizings can get a little wonky in LabVIEW. We'll see if we can fix this.
  16. My welcome screen looks ugly. Why is the font way too large for the allocated space, see picture? (LV 2019, Windows 10)?
  17. That would be great! Looking forward to seeing what you're been working on.
  18. I think I might be able to share this specific utility I'm working on. It's a very small piece in the big picture of what I'm working on, and I use little utilities like this to try out new toolkits, modules, or LabVIEW components to see what might be worth bringing into our more mainstream code. In this case, the utility I'm working on is an accuracy specification management tool. I can probably post a few screenshots and thoughts on the UI development once I finish it up.
  19. You're welcome, Nathan. Glad to hear that it worked! Thanks for posting all these questions and feedback as you're making progress and putting the Flat UI Controls and Design Palette through the paces. Your UI must really be coming along, and would love to see some examples of what you come up with, if you're able to share.
  20. Ah - yep, that worked! I usually try and keep my styles separate from the data types, rather than have my type defs styled a certain way, too. But I think for the convenience of not having to recreate my enum and still have it linked to the typedef then this is worth it. Thanks again Jim Edit: I opened my classic enum typdef, replaced it with the jki one, then to avoid replacing all instances of the type def with the JKI one, I went back to my front panel that I wanted to change, used the quick drop shortcut ctrl + p and selected my typedef. That replaced just the instances with the JKI enum, then I went back to my typedef and reverted it to the boring classic style.
  21. Ah, I got it... See if this works -- I just tried it on my computer and I think it does... 1) Open your type definition in the control editor (right click on it and choose Open Type Def.) 2) In the control editor, select the enum... 3) Follow steps #1-4 in my previous post. 4) Save+close the type definition Does that do it?
  22. The quick drop worked, but the replacement control was no longer linked to my typedef in the same way that the built-in quick drop replacement works. (The gif I recorded would have shown this)
  23. Hi Nathan. We implemented Ctrl+P to replace in the 1.0.1 release of JKI Design Palette. 1) Select the enum you want to replace. 2) Press Ctrl-Shift-Space to activate the JKI Design Palette 3) Type "enum" and then select the enum in JKI Flat UI Controls 2.0 (mouse or tab key) 4) Press Ctrl+P to replace the selected enum on your VI FP with the JKI Flat UI Controls 2.0 enum you just selected in the Design Palette. voilà!
  24. Also, I tried attaching a .gif of the behavior but the forum site kept giving error -200 and saying 'upload failed' - I tried another browser and had the same issue. Weird, since yesterday I was able to upload a gif no problem.
  25. I have a type def'd enum (not strict) and I want to change the style of it from classic to the JKI Flat one for my UI. Using a quick drop shortcut, I can easily change from system, to NXG, to classic, etc. The JKI flat controls don't show up in quick drop (as far as I can tell?) so I can't use the ctrl+p shortcut to replace it. I can use the right-click menu and navigate to where the control is on disk and replace it that way, but then it loses all of the items in the enumeration. Is there any way to support the same quick drop replacement shortcut to maintain enum items? (I know that I can use the Item Names property to recreate the enum, and that's what I did for my application, but it would be nice to have the same functionality for the Flat UI controls.)
  26. Hey Nathan, Here's a new version of that control that should fix the issue. Path--File-Browse-Folder-Location-Simple.ctl Replace the file, here, and you'll be all set: <LabVIEW>\resource\JKI\Design Palette\Themes\JKI Flat UI 2.0\Path--File-Browse-Folder-Location-Simple.ctl We'll have this fixed in the next official release of the JKI Flat UI Controls 2.0. Thanks again for your attention to these little details.
  27. Last week
  28. You're welcome and thanks for the add'l explanation about your applications and design approaches. I've been chatting a lot with @Eric Welden about all the great feedback we've been getting lately and one take-away for me has been that there are almost always some exceptions and creating a nice looking UI will most certainly involve a lot of customizations to a basic theme. So, the Flat UI Controls 2.0 will get you much of the way there (since it's a great baseline). *And*, to create a mind-blowing UI, you'll definitely want to have a designer tweak stuff and create some customized elements 🙂
  1. Load more activity
  • Create New...

Important Information

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