LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How do you handle your status string updates?

Richard and Jeff made a pretty snappy abstracted GUI tool.

 

Basically, all the functionality and the User Interface widget[s] itself is held inside an Action Engine, and the Action Engine is placed on the front panel as a sub VI. Anything can then write to the Action Engine without needing to worry about references, or even if the VI is even being used.

 

It may or may not be useful to your status bar, but it is certainly a different way of thinking about it all.

_____________________________
- Cheers, Ed
0 Kudos
Message 21 of 26
(697 Views)

@yenknip wrote:

Richard and Jeff made a pretty snappy abstracted GUI tool.

 

Basically, all the functionality and the User Interface widget[s] itself is held inside an Action Engine, and the Action Engine is placed on the front panel as a sub VI. Anything can then write to the Action Engine without needing to worry about references, or even if the VI is even being used.

 

It may or may not be useful to your status bar, but it is certainly a different way of thinking about it all.


I got something similar to that (if I understood it correctly) in my testcase executive example code. Using xcontrols and subpanels depending on the testcases.

 

https://decibel.ni.com/content/docs/DOC-24602

 

Br,

 

/Roger

 

Message 22 of 26
(691 Views)

@User002 wrote:

I got something similar to that (if I understood it correctly) in my testcase executive example code. Using xcontrols and subpanels depending on the testcases.

 

https://decibel.ni.com/content/docs/DOC-24602

 

Br,

 

/Roger

 


Yeah, that sounds similar. It's sort of like using an AE as an xcontrol

 

_____________________________
- Cheers, Ed
0 Kudos
Message 23 of 26
(686 Views)

@yenknip wrote:

Yeah, that sounds similar. It's sort of like using an AE as an xcontrol

 


I guess so, the xcontrol becomes initialized/registrers the classes (where the FP's are). Loads them up and puts them in an array of vi refs. The rest is straight-forward LV. Tucked away in a x-control for less property node bloat.

 

Br,

 

/Roger

 

0 Kudos
Message 24 of 26
(681 Views)

@User002 wrote:

@yenknip wrote:

Yeah, that sounds similar. It's sort of like using an AE as an xcontrol

 


I guess so, the xcontrol becomes initialized/registrers the classes (where the FP's are). Loads them up and puts them in an array of vi refs. The rest is straight-forward LV. Tucked away in a x-control for less property node bloat.

 

Br,

 

/Roger

 


 

 

Now its my turn.

 

Care to write a Nugget on that idea?

 

The feedback for interesting Nuggets usually makes the Nuggeteer more powerful.

 

Concider it please.

 

 

Ben

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 25 of 26
(664 Views)

  

Now its my turn.

 

Care to write a Nugget on that idea?

 

The feedback for interesting Nuggets usually makes the Nuggeteer more powerful.

 

Concider it please.

 

 

Ben

 


Okay, sure will do!

 

Though, first I have to xcontrol:ize my alarm/event handling and feedback control examples and put them up on the community.

Then I gotta go to NI days in Stockholm Sweden, to show off my side-project based on a sbRIO 9606 and some misc electronics.

 

UAV.jpg

 

I know there are a lot of rocket-engineers(scientists) working with LV. Now, it can't be that hard to control a flying winged UAV's compared with the stuff Elon Musk throws into orbit riding on pillars of fire. Smiley LOL

 

If anyone feels to write some nuggets regarding trajectory generation/control/path planning I'd be honoured to include it. Maybe there already are?

Of course everything will be/are opensourced.

 

Br,

 

/Roger

 

Message 26 of 26
(660 Views)