Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/23/2018 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. 1 point
    Hi not sure if I'm misunderstanding but what's the use of "I want different colors" and "allow interaction" ? I don't see any different behavior when clicking on the UIs in "interactive" and non-interactive mode (colors do work). I also don't understand the colors, when dragging a UI to a FP (with different color) it changes back to default colors on the FP. Also "Allow interaction" - checkbox and left color box collide (see picture). Last but not least: how do you exit interactive and color mode? I had to restart LabVIEW. Regards Christioh
  5. 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
  6. 1 point
    Looks like the newest version fixed it. Thanks!
  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
    Hi Jim, I just checked and it works great! Good idea to automatically delete the "Delete Me" element once the control is placed on the Front Panel. It also looks like the issue with the controls disappearing doesn't exist anymore. Thanks
  9. 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!
  10. 1 point
    The design palette seems to work well for Boolean buttons, but is more difficult to use for other controls. For example, if I type "graph" I get firstly various buttons, then a number of graphs, but there's no way to tell what type of graph: waveform, XY, Intensity - even a chart gets shown here (because the filename on disk includes the word "Graph"). Suggested enhancements: text showing the name of the control currently selected (or under the pointer) in the same way as the LV Control menus the list of control types filtered to show only those which are part of the current search (same as the sizes are only those relevant) where the search text is a standard control type, then those are shown first before buttons that also match the text - and/or ability to sort by type rather than theme a list of other words relevant to the current search that can quickly be clicked on to limit the options shown, either sorted alphabetically or by frequency of use
  11. 1 point
    Local configuration, FYI: Windows 10 font scaling is at 100% LabVIEW fonts are all defined as "tahoma 13" in ini.
  12. 1 point
    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.
  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
    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?
  15. 1 point
    Right-clicking on the button also doesn't provide the menu option 'Browse Options.' You have to right-click in the path area itself to select that.
  16. 1 point
  17. 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?
  18. 1 point
    A mouse over hover effect has become standard in most major software UIs. This effect allows users to interact with controls in a more intuitive way and gives users confidence that they are making the selection that they intend. However there is a long standing NI bug that renders the hover effect inconsistent (see the discussion here: https://forums.ni.com/t5/LabVIEW/Button-Boolean-mouse-hover-not-working-on-64-Bit-LabVIEW/m-p/3944252#M1121887) Until NI makes a fix one 'solution' that I will employ is to disable the hover effect with the controls that I am using so that users do not get confused by a control stuck in a hover state.
  19. 1 point
    So far it looks like issue is not existing anymore. Thanks
  20. 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.
  21. 1 point
    I knew there should be an alternative 🤓
  22. 1 point
    Show Labels of All Controls in the JKI SDP (Ctrl+L) You can show or hide the labels of all the controls in the JKI SDP by pressing Ctrl+L. Press Ctrl+L to show labels on all the controls: Press Ctrl+L again to hide the labels
  23. 1 point
    I used the previous "light" themed Flat UI Controls in my application and was excited about the update. There is no "light" theme in Flat UI 2.0 (or I'm missing something)? Regards Christoph
  24. 1 point
    Hi Volks, i've tried out the new Flat UI 2.0 Controls. Therefore I installed the package using VIPM. First of all I found it quite annoying that every time labview starts the window with the control platte popped up and there's no quick to find way to disable this hence i uninstalled it. Every time I try to compile an application or start labview I'll get another annoying message: Can you name me a fix for this issue? I've no idea where the new control palette nested in. Thank you very much. Nice greetings and thank you for sharing your outstanding plugins / VIs 🙂
  25. 1 point
    The design palette shows up every time I open a LabVIEW project, is it the intended behavior? And is it possible to change this? Cheers
  26. 1 point
    Yes, issue resolved! Thanks for fixing it so fast. 👍
  27. 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
  28. 1 point
    DP.mp4 it also shows up at unexpected moments, e.g when doing a save all from the lvproj window see video
  29. 1 point
  30. 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.
  31. 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)
  32. 1 point
    Dear JKI Team, unfortunately the VIPM could not download the JKI Design Palette from the remote server. No problems with other packages. Kind regards from Germany and thanks for your really great tools! Peter
  33. 1 point
    I ran across a problem in a project where, after creating and initializing the class under test in the setUp VI, unbundling it in the test VI returns a default object rather than the one I instantiated. setUp.vi testCount.vi I've attached a project with the class under test (ListImp) and two test cases. Both test cases have (as near as I can tell) identical setUp code and identical code in the test method (testCount). However, one test passes while the other test fails. Any idea what's causing this? [Edit - The about box reports "version 3.0.1.294 (Feb 11 2019)".] [Edit 2 - Another piece of potentially relevant information is the Test_ListImp..._2 test class was brought forward from an older version of VI Tester. I don't know what version, but according to my repository it was sometime before Feb. 2013. The other test class (the one that passed) was created with the current version of VI Tester.] VI Tester Error.zip
  34. 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.
  35. 1 point
    Hi JKI team, Firstly I want to thank you for generating the REST toolkit for LabVIEW, it seems pretty easy to connect the IoT cloud. I do, have some glitches when using it. I came across to this youtube demo ( Are you able to make an example to show how to use the tool? If that takes a while, would you please comment on 1. What's the input of Base URL? I used "api.favoriot.com" in my case. 2. Do you define the apiKey in one of the Default Headers? I did this but didn't seem to get anywhere. Your help is appreciated.
  36. 1 point
    Never mind. It appears my JKI state machine was a older version after the upgrade I was able to access explorer option.
  37. 1 point
    Hello everyone, Fist of all thank you for your Tools that are very helpfull. I'm trying to use the HTTP JKI REST drivers with an HTTPS website but I need to go trough a Proxy. How is it possible to desribe the PROXY settings with this driver? Thank you by advance.
  38. 1 point
    Hello! Where can I download the latest versions of the state machine and the state machine editor as a vip file (there is no Internet access on that computer)? Or maybe you can get out of any directory when installing via vipm? https://github.com/JKISoftware/JKI-State-Machine/releases? here?
  39. 1 point
    Hi @Antoine Chalons. Yes, I can see how layers of nested array/cluster containers can be tricky 🙂 I'm glad you were able to figure it out, and get it working! Hope all is going well for you in general and on your LV projects.
  40. 1 point
    Open "Compare to Constant.xnode" with a text editor. Near the bottom, delete the two items "Untitled 4 (SubVI)" and "Untitled 5 (SubVI)" Then it will build.
  41. 1 point
    single step sounds good - and should work in both direction Last/Next Step dynamic state generation - maybe JSON imported State"Objects" (export fct would be nice 2)
  42. 1 point
  43. 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.
  44. 1 point
    Hi @Jim Kring , I have tried out the new build(3.0.2) and it works fine for me. Thanks for the immediate fix Thanks, Bhargavi Gowri.
  45. 1 point
    Hi @JimKring I have attached the sample project, which demonstrates the issue that I am facing. I have also attached the image, which shows the DOM ref values in New.vi of test suite and setUp.vi of the test case. Please let me know if you need any details. Thanks, Bhargavi Gowri. Sample Code.zip
  46. 1 point
    Hello, I am having trouble loading tests. When VI tester starts it doesn't find my tests. I can manually load 1 test by File/Open File or test class. I can't load multiple tests. I have my classes in folders. Do the test classes need to be in the top level of my project? I have them in a auto populating folder called "Unit tests? Thanks Dan
  47. 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.
  48. 1 point
    Yep, the new version works well. Many thanks!
  49. 1 point
    No, CPU usage is high all of the time. Yes, Mass Compile is enabled (always). I reinstalled JKI State Machine, but still nothing. So, I have to remember to close the Block Diagram first or JKI SM Editor (Explorer in fact...). Maybe it is important or not... my LabVIEW version is 2018 (18.0f2)
  50. 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
×
×
  • Create New...

Important Information

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