Search the Community
Showing results for tags 'xcontrols'.
Found 3 results
-
The QControl Toolkit by Q Software Innovations is an object-oriented and extensible alternative to XControls. Use the QControl Toolkit framework and the QControl Creation Wizard to create QControl Classes and receive the benefits of XControls without the headaches. Take advantage of easy UI logic code reuse. Encapsulate and decouple the UI logic away from the business logic of the main application and from the UI skin. Use wherever the VI Server and LabVIEW object-oriented programming are allowed. Easily extend the capabilities of current LabVIEW controls through access to all properties available at run time. And easily use the toolkit with more complex frameworks like the Actor Framework or other plugin architectures where LabVIEW libraries and packed project libraries are used and where XControls can behave unpredictably. Check it out now on the NI Tools Network here. I also started a thread on the NI Community: UI Interest Group page, here.
-
.thumb.png.d7c7b190a318a5aa97c6dd482546d474.png)
Hello all, I have a VI in LabVIEW 8.2 that includes more than 400 Xcontrols in nested tabs, which opens in seconds (very fast). The code was upgraded to LabVIEW 2013 and now the VI takes minutes to open and in the meantime LabVIEW is unusable with the CPU at 100%. I am wondering if anybody has experienced this behavior with Xcontrols. Thanks. Cross-posted to NI Forums -
When (in edit mode) you click on the border of a regular control it becomes selected.Not so for all XControls I've seen or created so far. The only way I found to mimic the behavior is to use Control refnum from the container state cluster and set "selected" (Scripting enabled) property to true. Questions: 1. Is it safe to do so, as I recollect there some synchronization related limitations on what you can do with this refnum. 2. Do I really have to enable scripting; am I missing some much easier way to do it?
