How to keep track of multiple UI control references

[doradorachan]

Hey guys,

 

So I was just looking through one of the presentations of NI Week 2014,

and this one talks about some cool tricks about UI.

 

Creating Highly Innovative User Interfaces With LabVIEW - Demos

 

My question is about specifically about one of the demos.

In one of his demo, he talks about an alternative way of storing UI refs compared to the typical "Create UI refs and store them into a cluster,

then unbundle the cluster when you need the UI refs"

 

I was just wondering if anybody had another way of controlling UIs.

I still use the cluster method but sometimes it takes a lot of spaces in the block diagram and was wondering if there was a better way

[LogMAN]

In one of my recent projects I used an actor (based on NI's actor model) to update UI elements. It basically consists of a class with all necessary control references in the private data (accessible only before launching the actor by using property nodes). Messages were implemented to update each specific control. Due to that it was possible to update the UI without blocking tasks, since the UI thread was handled by the actor core.

[ShaunR]

I'm rather fond of applying behaviours en masse via callbacks.

 

Ctrl CB.zip

[doradorachan]

LogMAN,

 

Actor model is something I definitely want to learn about... but I'm still in the process of learning oop 

 

ShaunR,

 

That is pretty darn cool!

[ShaunR]

 

ShaunR,

 

That is pretty darn cool!

 

Now you know how to make all your string controls/indicators URL aware without faffing around with xControls or cluttering up yer main diagram

Edited September 16, 2014 by ShaunR