08-05-2013 10:34 AM
Hello,
I started a vi based on an event structure where the events are button pushes. The code works fine. I would like to add an additional 'Start' button that would perform the individual events. Any help or direction you can provide would be greatly appreciated.
08-05-2013 10:41 AM - edited 08-05-2013 10:43 AM
Sounds like you could be after a state machine, or event driven queued state machine.
Do you just want to be able to click your start button and then have it cycle through your sequence in order or do you want to be able to execute the individial items in the sequence separatly and out of order?
Look up 'State Machine' for the click start, and leave it option, or 'Queued State Machine' / 'Producer Consumer' if you want to be able to pick states out of order, and also have an option to automatically cycle through.
Hope that makes sense.
p.s. if you are using LV2012/13 I think there are some templates that would be suitable to get you started
08-05-2013 10:46 AM
Thanks, I'll look into the secdond option.
08-06-2013 06:45 AM
This is sounding like an ideal case for the QSM, or as many of us are trying to get it renamed to Queued Message Handler.
08-06-2013 08:59 AM - edited 08-06-2013 09:00 AM
Not that architectures like state machines and queued message handlers aren't great, but if all one needs is to add a button that triggers other already-coded-for buttons then one can use Value(signalling) Property nodes.
08-06-2013 09:03 AM
@crossrulz wrote:
This is sounding like an ideal case for the QSM, or as many of us are trying to get it renamed to Queued Message Handler.
Reading the new pages about LV2013, it looks like you have been heard.
Cameron
08-06-2013 11:46 AM
@drjdpowell wrote:
Not that architectures like state machines and queued message handlers aren't great, but if all one needs is to add a button that triggers other already-coded-for buttons then one can use Value(signalling) Property nodes.
I was thinking the same thing, although it'd be slightly prettier to remove those buttons and move the functionality to a User event.
/Y