Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/06/2010 in all areas

  1. 2 points
    Nice. The empty clusters and arrays now work without issues! Here is a suggestion for the existing clusters/arrays that contain a delete me button (in case you need to keep it after the latest upgrade): why not make the text hidden and the color transparent so it won't even appear (since it is going to be deleted anyway) And for the decorations, I suggest that you put the decoration on top of an transparent empty cluster that will get deleted after being placed on the FP (in a similar approach to the above).
  2. 2 points
    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. 2 points
    Ideas and Features: Add other commonly used controls that aren't supported Clusters, arrays, subpanels, decorations, etc. Add more advanced controls Animated Menu Toggled controls (such as one button that does start + stop function) Custom Radio Selectors (paging/tabbing) Draggable Navbar UI templates Merge VIs Other commonly used modern UI building blocks Let us know if you have any others! Post an Idea or Feature Request Now.
  4. 2 points
    Get the JKI State Machine Editor (just check VIPM for package updates) Version 2013.4.0.186 This new release adds a right-click option called "Find Data Accessors" to Bundle by Name and Unbundle by Name nodes in a JKI State Machine. Using this feature will open a dialog showing all the frames of the JKI State Machine that access the data, as shown below:
  5. 2 points
    I found one problem that occurs to me. "Find Data Accessors" is available in any VI (not only JKI State Machine) for the Unbudle by Name function, but its call does not cause the appropriate list to be displayed in the dialog box, although the application is started and consumes processor resources. Calling it several times on a notebook with an i5-4210M processor results in 100% CPU load. I've attached a screenshot for the FMSM example from LabVIEW example projects. As you can see, also Add Dynamic Events and JKI State Machine Editor... are visible - only when pop-up on Bundle/Unbundle by Name.
  6. 1 point
    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
  7. 1 point
    Thanks for testing and letting us know. Yes, we now officially support "empty" clusters and arrays -- previously, these were throwing errors when we tried to load them, but we fixed it so that they are handled better and officially supported. Have fun.
  8. 1 point
    The default icon for the Flat Path Control is the 'Add' icon. I would expect it to be something more an Open Folder icon, as in the System Path Control in Windows 10.
  9. 1 point
    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. 1 point
    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!
  11. 1 point
    Hello JKI Team & Community, I'm having trouble activating the JKI Design Palette, specifically requesting the activation code. Labview throws an Network Time Limit Error when submitting the mail adress (see attached image). The error is consistent within the corporate network (proxy/firewall) and on the unrestricted mobile hotspot. Using Windows 10, Labview 2015 (32bit) Looking forward to trying the new controls, Cheers
  12. 1 point
    Local configuration, FYI: Windows 10 font scaling is at 100% LabVIEW fonts are all defined as "tahoma 13" in ini.
  13. 1 point
    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.
  14. 1 point
    I get this error when trying to submit feedback from the Design Palette: Could be related to me having to do an offline activation?
  15. 1 point
    Yes, I meant Quick Drop, but couldn't remember its proper name. I'm using the latest version of JKI Design Palette. However, the problem disappeared. It seems that it disappeared after I first tried Ctrl+Alt+Space to pop up the Design Palette. After that Ctrl+Space correctly opens Quick Drop window.
  16. 1 point
    An easy way to do a super simple resizeable UI, I think, is to use splitter bars and then choose one pane that has some kind of big UI element that is easy to resize like a graph that you can just set as "size to pane". Then set the sticking of the splitter bars so that one pane is the only one that changes size on panel resize events and all others stay the same. Then you don't have to worry about scaling all the little buttons and dealing with decorations getting pixelated. But for a tab control, yeah there is no easy way sadly (at least that I know of). For this, I usually just use radio buttons as the tabs and then a subpanel and switch out which VI is displayed in the subpanel based on the radio buttons.
  17. 1 point
    I knew there should be an alternative 🤓
  18. 1 point
    Hi Jim, thank you the error has gone.
  19. 1 point
    Hi @Antoine Chalons. Can you please try out the new 1.0.1 release and let us know if this resolves your issue. I think we've fixed it, and would love to hear your feedback.
  20. 1 point
    I am getting this error when I start labview (2018 64bit). If I even do a search for that file I don't find it anywhere
  21. 1 point
    DP.mp4 it also shows up at unexpected moments, e.g when doing a save all from the lvproj window see video
  22. 1 point
    Yes, when the DP shows up as I open a project it is pinned. See attached video : I have a small project already open with the main.vi running Then open a DQMH project >> DP shows up pinned Untitled.mp4
  23. 1 point
    I suspected that but could not pinpoint which one could be causing the issue. I monitored the memory consumption to see if it is spiking during scrolling but it is not. I am not able to scroll all the way in neither classic nor Flat... And out of no where, i am sometimes getting the error below (even when the design palette is not open). I guess the palette continuously check for communication with the server in the background for some reason. Ali
  24. 1 point
    It wasn't my video, just a forum topic of the tool i'm using. You can find my recorded example below. Even though I unpin the palette and close the window, it is still being opened.
  25. 1 point
    Hi Jim Yes i am able to use the palette if not scrolling. It is not freezing after a period of time. Below are also some observations: The palette will freeze if I: Select "System theme" from the combo box (the classic and flat works fine) Maximize the palette The palette will NOT freeze if a I scroll with a limited number of controls shown (for example when filtering to show only boolean controls)
  26. 1 point
    Can i Link this case structure viewer to my existing case structure. i already created one VI using Enum based state machine.Now i want to convert it to JKI state machine.is there any possibility to convert with minimum changes instead of re-implementing.
  27. 1 point
    I have installed LABVIEW 2019, and I followed the procedures to make sure VIPM can communicate with VIPM 2018.0.0f2: https://support.jki.net/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW But, still I do not see LABVIEW 2019 listed within the VIPM window: Any clue on how o solve this? Thanks
  28. 1 point
    I had a separate QD plugin for this, but I can't find evidence that I ever shared it with the community. You've just given "ctrl+space ctrl+q" back to me. Thank you. However, mine puts it exactly eight pixels from the output tunnel and pre-wires an empty String constant... Another feature to add might be my JKI State Machine Follower. It activates the current Case Structure case while the VI is running. Maybe? You'll save me "ctrl+space ctrl+f"... Thanks for all your work on this, Jim
  29. 1 point
    Hi all, I have faced an issue with JKI VI Tester. Here are the details.. I am creating a DOM reference in "Setup.vi" and bundling it into my TestCase Object. DOM reference can be created by using "Load.vi" from XML Parser palette(attached image-> XML Parser palette and DOM Ref.png). When I unbundle it in the test VI, the DOM is reset to '0'. It is getting lost. We digged into the VI Tester and found out that some deprecated property nodes are used in "_JKI Toolkits\VI Tester\TestCase.llb\CallTestMethod.vi" in order to pass data from one VI (Setup VI) to another VI (Test VI).Refer to attached images -> VI Tester_Set Control.png, VI Tester_Get All.png. When the DOM reference is flattened it is getting lost, because LabVIEW doesn't know how to convert DOM reference into flattened data type. We have done a quick internal fix by replacing the property nodes and using variant to data after getting the control value. These changes are shown in "VI Tester_Set Changed.png" and "VI Tester_Get_Changed.png". Also, in "_JKI Toolkits\VI Tester\TestCase.llb\WaitOnTestComplete.vi", we have replaced the property node when parent data is written to child class indicator. This change is shown in "WaitOnTestComplete.png". I am getting my DOM reference in test VI correctly after doing this change. As I said this is a quick fix done for internal purpose. If this is the right change to make it work, can you please make this change and distribute the package so that my customers can also use it. If this is not the right change to be made, please suggest us how to fix this. Also, let me know if you can fix this issue and and release the fixed version. Please let me know if any other information is needed regarding this. Thanks, Bhargavi Gowri.
  30. 1 point
    @Jim Kring I realize that this comment is almost 8 years later, but I can confirm that the UI does not appear to find any tests in classes contained in auto-populating folders.
  31. 1 point
    @Robert Smith I know this is four years later and probably not very helpful, but I just used VI Tester for the first time and found that my tests would not appear in the UI if the test classes were in auto-populating folders. This may have been your problem. Hopefully this helps someone else who might come across this thread.
  32. 1 point
    Ruslan, I will suggest to leverage VIPM's capability. Refer this link: https://support.jki.net/hc/en-us/articles/214135803-How-do-I-transfer-packages-with-VIPM-to-a-non-networked-computer-
  33. 1 point
    I've got a problem with JKI SM Editor (JKI SM ver. 2018). In one case, it increases the CPU resources consumption. The procedure is as follow: 1. Open New VI or existing VI with JKI SM. 2. Open block diagram. 3. Open JKI SM Editor. 4. Close front panel of the VI. CPU usage increases - in my case (i5-4210M) up to 38 - 40%. Have to reset the LabVIEW. Has anyone observed silmilar behaviour? [Update: This has been fixed in version 2018.0.1.36 of the JKI State Machine package, which has been published and is available for download and installation using VIPM.]
  34. 1 point
    Yep, the new version works well. Many thanks!
  35. 1 point
    Hi, Please help... I am trying to create a .vip that will install my LabVIEW project as a LabVIEW project template (note: I have done this process a few time before with no issues) I have my project that I want to make into a template, everything works perfectly. I configure the .vipb, I build and install the .vip. I check the destination to see if my files have installed to the correct location, they have. Here's where the problem kicks in...... I open my LabVIEW project that has installed in the destination, and notice that the .png files in my project some are missing and some are saying missing. In my project I have .png files in various .lvlibs. The first .lvlib in the project has the .png's showing, however showing as missing and the expected location is saying C:\ which is incorrect, it should be in the location where my .lvlib is in the destination. The other .lvlib's don't even show the .pngs in the LabVIEW project explorer. Now checking on disk all the png's are there and in the correct location. In summary it looks as if as part of the vip install it is removing the link the .lvproj has to my .png files VI Package Manager Version : 2018.0.0f1 Jul 21 2018 LabVIEW Version : 2016 (32 bit) OS : Windows 10 Pro Version 1803 Any help is greatly appreciated Thanks in advance. Kev
  36. 1 point
    Jim, Here is a simple example. Note it appears that also text files (and perhaps any non-LV files) are affected. The .vipb file is from 2017. Sam Simple Example.zip
  37. 1 point
    Hi Ashish, I have and thank you so much for sending the link. I am happy to say that the problem is fixed and I am able to use VIPM without any issues at this moment. We use Kaspersky Endpoint Security 10 and added VIPM as an exception within Kaspersky and that is why I was unable to achieve a connection with LabVIEW.
  38. 1 point
    So I often leave VIP builder open when I'm working on a package that's being rebuilt multiple times whilst I work out bugs and issues. If I leave VIP Builder open overnight on my PC (Windows 7 SP1) then the following morning, as soon as I edit the Build Specification and click Save I get a cyclical error code 1 that I cannot close and I'm forced to kill VIPM.
  39. 1 point
    Update from JKI: This issue is planned to been fixed in VIPM 2018. So I can successfully build packages with VIMs in them. But I found that if I need to make a package, that depends on a package, which contains a VIM, the build will fail. First install the hooovahh_array_vims-1.0.0.6 package. Then try to build the File IO package, which at the moment only contains one VI. If it is like my setup the build will fail with this error. If I remove the VIM dependency by replacing it with the OpenG one the build is successful. Build Fail VIM Dependency.zip
  40. 1 point
    Thank you for giving me hope and help! Kindest Regards, Brian
  41. 1 point
    Thanks, Jim. That's great news. I'm not sure whether it addresses Fab's concerns, but it does address mine. I'll let you know if I encounter any issues with VIPM 2017 for Linux. -Chris
  42. 1 point
    @Jim Kring Ahaaaa- in my case, that folder already existed from a previous install; and the jki.conf it contained was owned (755) by the previous user of my machine... I recursively gave myself permissions through the whole folder, which cured the error 8; however, VIPM would then launch, and die silently while still at the splash screen.. So I blow away the whole JKI folder, and everything went fine from a clean start ;-) -Thanks for your help! ~Tom
  43. 1 point
    The OpenG Array Library 4.1.1.14 is not listed in VIPM from the JKI Package Network. I even tried refreshing, but it did not find the required library. Other observations: 1. I am able to see an older version 4.1.0.13 of that library in VIPM 2. I checked the website and was able to find the latest version But I want to understand why my VIPM is not listing it
  44. 1 point
  45. 1 point
    One of my colleagues almost fell down; he was so happy when I showed him this new feature. Excellent idea & implementation.
  46. 1 point
    Whoops, my bad. I don't really know VIPM very well. My co worker wrote: "I think you're looking at a re-packaged version of JKI VI Tester for MacOS that I made locally. VI Tester still shouldn't be available for mac through VIPM. "
  47. 1 point
    I installed VIPM (2014 because that's the latest build for Mac) on MacOS. It's showing plenty of packages such as ones from NI, MGI, etc... But oddly, no JKI packages. So I can't find VI tester in the list. Any idea what could be causing that?
  48. 1 point
    Thanks @Jim Kring for the quick response! Glad I wasn't crazy for thinking it could be done "in theory". My team is definitely in need of VIPM pro but in the near future we would need a way to automate applying vipc files during our build process. Using command line is actually great for our purposes.
  49. 1 point
    Yes I can see the JKI packages. I noticed there appears to now be a "MacOS JKI VI Tester" package
  50. 1 point
    It worked. Only issue is when opening the visual tester it looks for some stuff from registry.llb (or dll I can't remember) and I have to ignore it, but the tester ran fine after ignoring those files.
×
×
  • Create New...

Important Information

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