Hi jhaysonn,

What about this:

i did not look at your patch, but the only chance is to ask for parameter #3 every 50 ms - until you get a response.

I think you could simply use [deferlow]. For me it seems to work like this

does [deferlow] step through the [trigger] like that? Waiting for the action on the other end to finish? I do believe I feel safest using Alexis' method, as it feels more transparent. I was doing something like what you, Roman, suggested but without the metro - it seemed to keep requesting the params (a bug?) until the program was finished loading and then I got the params dump.

thanks! Its wild how everytime I think I understand something, and will even have it working - undoubtedly someone on these forums knows a better way to do it!

You don't need the deferlow either.

edit....

Actually the deferlow is right sometimes. If you can't guarantee that the plug message will be sent at low priority, you will need to put a deferlow before the trigger.

-A

Thanks Andrew for clarifying and confirming the simple trigger method.

word. I put some deferlows before the (too many and too large) [trigger]'s I was using and voila =) smooooooth operator =)