Hey skillet,
Too much info in help situations is nearly always better than too little.
Well organized is even better.
Always remember that your audience may never have seen your problem and try to give them enough information to understand the process.
Think of it this way:
I never want to see just the rate/time problem all written out.
I want to see the vehicle and the course - because very often I immediately see there's an unused nitrous tank on the vehicle and a giant shortcut in the course.
The written problem usually misses all of those things.
The author usually leaves things out, because (s)he already knows the problem pretty well and makes incorrect assumptions about what someone else needs to know to help.
I know this well, because I've been helped and given help on the Net for over 20 years.
Just knowing you're working in Cubase 8 lets me look at it on the Web to get an idea of what you're dealing with, and that changes my perception of the problem considerably.
Back to your problem.
You can always set a variable like completionFlagVar to false and then set it to true if your conditional evaluates true.
Set completionFlagVar to FALSE
If All Conditions Met Execute Actions:
Your conditional
If TRUE then:
x
y
z
Set completionFlagVar to TRUE
Otherwise Execute the Following Actions
Set completionFlagVar to FALSE
If All Conditions Met Execute Actions:
If completionFlagVar is FALSE
Do something…
You can group your conditionals in many ways for quite a lot of flexibility.
I'm not certain what the TriggerResult text token does and have a question in to Peter about it. I think maybe he mistyped, but we'll see.
Peter has indicated significant improvement for 'Found Images' in KM7, but unfortunately we'll have to wait some time to see them.
Okay. Hopefully my rambling has added some meat to the pot.
-ccs