From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
11-17-2009 06:08 AM
Hi
Since this looks more and more like a structure discussion I recommend having a look at Bens excellent nugget on action engines. You're already heading in that direction so this is a good source for information and inspiration.
jcarmody wrote:
You can wrap your uninteresting code in a Flat Sequence, turn Auto Grow off and shrink it. Then, when you want to look inside you just resize it (or, turn Auto Grow back on). I've heard of that being done, with the developer pleased that the entire program fit on one screen!
That could be the silliest thing I've heard yet
Best Regards
David
NISW
11-17-2009 06:30 AM
11-17-2009 07:19 AM
jcarmody wrote:
You can wrap your uninteresting code in a Flat Sequence, turn Auto Grow off and shrink it. Then, when you want to look inside you just resize it (or, turn Auto Grow back on). I've heard of that being done, with the developer pleased that the entire program fit on one screen!
I really hope you were kidding. This is a terrible suggestion. The last thing we should be doing is telling be to have hidden code in their block diagrams.
11-17-2009 07:51 AM
Mark Yedinak wrote:
I really hope you were kidding. This is a terrible suggestion.
I've been told that it's hard to tell when I'm kidding, but COME ON!!! That's the most ridiculous idea I could come up with!
I'm sorry for not using an emoticon.
11-17-2009 11:21 AM
11-18-2009 01:24 AM
I sincerely hope they read on for a bit in the thread in that case. Once more for emphasis: Don't try this at home kids
/David
11-18-2009 08:45 AM
In 25 words or less...
If you run your code in the event itself, no other events can be processed until the code is completed.
11-18-2009 08:51 AM
Queue in 25 words or less:
Establish Queue for states:
Events add next state name to Queue
Event ready for next event
State Machine runs next state name from Queue
Hummer1
11-18-2009 08:57 AM - edited 11-18-2009 08:58 AM
Davidek wrote:I sincerely hope they read on for a bit in the thread in that case. Once more for emphasis: Don't try this at home kids
/David
I reported my post to the moderator and had a disclaimer added. We're safe now!
Edit - I won't make THAT mistake again.
10-10-2011 12:22 PM
I think this is a job for subVIs. If there is a reason this cannot be done you have a real problem on your hands.
It may just possibly be that the logic cannot be neatly divided into subVIs, if this is true, your problem is bigger.