Search the Community
Showing results for tags 'controls'.
Found 3 results
Hello Everyone, I noticed an interesting change today that I thought was worth mentioning. I've been using the classic system button for some of my UI's. It's flat and looks clean. Less busy. I noticed today that the graphics for this button are different from one of my PC's to another. My laptop, which is running 2016.0, looks like the original. My desktop which is running 2016.0f2 looks like the 'different' one. Both 2016 but one has no depth graphic and one does. I've dug through the menus folder and it looks like the classic and modern controls are not housed there, which makes sense really since they are probably proprietary. I'd prefer the original look as it matches with the flat Windows 10 style that's in vogue right now. Just something I noticed and thought was worth mentioning. Cheers, Tim
The attached VIPM contains an extension of Messenger Library that is intended to add extended functionality to controls/indicators, via a background process that is launched and which registers for the events of the control (the background process is a Messenger-Library “actor”). This is meant to be an alternative to XControls. Included are two “Augments”, both with examples. See <examples>/drjdpowell/UI Augments/Examples/EXAMPLE Twin Cursor Graph Augment. This takes any graph with two cursors and draws a line between the two and displays summary info of the data between the two cursors: There is also a cross-section plotting for a 2D intensity chart: This package is in LabVIEW 2015, and requires Messenger Library (latest, in the LAVA-CR) and JSON LabVIEW and Shortcut menu from Cluster (both in the LAVA-CR). drjdpowell_messenger_ui_augments-184.108.40.206.vip
Dear LabVIEW community! I have installed LabVIEW, v13.0f02, 32-bit on my PC. The problem, which I face, is that DAQmx Physical Channel controls, which are used in VIs inside the LV projects, sometimes don't show me the list of DAQ devices - I can't expand the list at all. I push the button to expand the list, but nothing helps. But when I create VIs outside the project, and put there DAQmx Physical Channel control - everything works well. Note: devices are simulated via MAX. Is it some kind of bug in 2013 vesrion of LabVIEW? Because while using LV 2012 I didn't have such headache. The only thing that helps now - is to restart PC (laptop) several times; b/c restart of LV doesn't help. Can anyone suggest, what it can be, and how to fix this problem? Thank you very much in advance!