Jump to content

nathan-murphy

Members
  • Content Count

    31
  • Joined

  • Last visited

  • Days Won

    4

nathan-murphy last won the day on April 4

nathan-murphy had the most liked content!

Community Reputation

18 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Running as Admin worked - but that's a nasty workaround that I don't really want to continue having to do. Appreciate any thoughts or if there's any debug info that you want me to share.
  2. Hey all - anyone seen this issue? I installed VIPM 2020 as part of a LabVIEW 2020 installation from NI Package Manager. When I tried to launch VIPM I went through the setup options, selected Free User, and selected to Sign in later. Then VIPM went to the splash screen, the loading bar made it about halfway across, and then the window just closed. No errors, no indication of what might have failed. Thinking it was an installation issue, I downloaded the latest VIPM from JKI.net and tried again - this time I wasn't prompted for what kind of user I was, but the window closed again at the same location. Next, I used the Windows 10 Add or Remove Programs menu to uninstall VIPM, searched in NI Package Manager for VIPM, and used the "Remove" option to uninstall it there too. Rebooted the PC, and tried installing VIPM from the same download from JKI. After reinstalled, rebooted the PC, and saw the same error. GIF attached for reference. I exported a screenshot from the GIF to see which VI was failing. That's attached, too. Any thoughts to how I can get VIPM to launch?
  3. In my case, the Main UI doesn't really do anything in the background, so I didn't have to worry about it blocking. If you have a case where you have a running VI that needs to continue to load, you can call the dialog window by reference using an Asynchronous call by reference, and check to see if the VI has finished executing in the timeout case of the Main VI (assuming the Main VI is something similar to a JKI State Machine).
  4. No problem, and you're absolutely right about the boolean text.
  5. Hey Ruslan, Thanks - I was able to take that dialog window out of my project pretty easily. Not sure what version of LabVIEW you're using, so I saved it back for 2013 just in case. The one dialog window is effectively two clusters stacked on top of each other. First I make the selection cluster visible, then when a user selects which option they want, I hide that cluster and the Name and Apply buttons are visible beneath it. Happy to answer any questions you've got on it. -Nate Add New Specification.vi
  6. Hey Ruslan, What specifically do you like about it? Anything you dislike or don't agree with? I can probably share my front panels so you can play with the colors, etc. but I don't think I can share the code due to the NDA/IP rights with my company. If you're looking for something in particular about it I can probably share a screenshot or explain how/why I did certain things. The actual code isn't really all that magical. I think it's just a JKI State Machine doing some logic to get data to and from a file. -Nate
  7. Not a good sign that there were no replies here, but it's worth a shot. After successfully building my application for months, I am also now getting this same error on the same VI. Were you ever able to find a resolution to the problem?
  8. You're really making me think harder now about my cons and wishlists! Thanks to you and the team for the continued refinement of the tool!
  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. 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.
  11. 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.
  12. 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)
  13. 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.
  14. 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.)
  15. Story of my life when dealing with LabVIEW UI elements... Thanks for the explanation - I'll keep that in mind when placing buttons on my UI. I tend to put icon-only buttons in the horizontal mode for space saving, or I'll put the text underneath an icon similar to the ribbon in Microsoft Applications, or the left-bar in their newer applications (Teams). Combination of icon and text center aligned in a Laid Out Horizontally layout, and stacked vertically in the same space: Icons and Text all center aligned: Of course, this all heavily depends on how the user plans on interacting with the UI. In my case, the applications I'm working on a very document centric and have lots of configurations and menus, similar to Office applications. To keep the layout familiar to the user, I mimicked the Ribbon and File Menu ideas. Thanks for being so receptive to the feedback. I can tell just how much painstaking pixel pushing work went into these UI elements and am really loving the look and feel (and built-in color customization!) of the new controls.
×
×
  • Create New...

Important Information

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