Action Engine

[Phillip Brooks]

I'm involved in a new project where I will be using templates. These templates make use of sub-vis referred to as Action Engines. I've searched various LabVIEW materials, Google and (most importantly) the LAVA Forums. I can't find any references to an Action Engine implementation.

It appears that these action engines are passed references to front panel vis and contain uninitialized shift registers. the Actions are enumerated, and current states are returned as outputs. I understand how they work, but where does this term Action Engine com from?

I did see a couple of posts on comp.lang.labview regarding action engines.

[Phillip Brooks]

I'm involved in a new project where I will be using templates. These templates make use of sub-vis referred to as Action Engines. I've searched various LabVIEW materials, Google and (most importantly) the LAVA Forums. I can't find any references to an Action Engine implementation.

It appears that these action engines are passed references to front panel vis and contain uninitialized shift registers. the Actions are enumerated, and current states are returned as outputs. I understand how they work, but where does this term Action Engine com from?

I did see a couple of posts on comp.lang.labview regarding action engines.

4571[/snapback]

Well, after reading the comp.lang.labview threads a bit closer, then action engine is really just a "functional global". I've ONLY been using LabVIEW since 5.1, and never been exposed to the LV2 or functional global concept. I understood the concept, but the term "action engine" bothered me.

The answer (for me) is here: http://forums.lavausergroup.org/index.php?showtopic=273