Pending messages

Ken Ray kray at sonsothunder.com
Thu Jun 17 18:38:00 EDT 2004


As Dar said, when you "send in time" and get the result, you get the message
ID number (I believe), so you could store that ID number along with the
parameters passed in a separate custom property or global variable and then
use the ID number in pendingMessages as a lookup.

HTH,

Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/


> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com 
> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of 
> Troy Rollins
> Sent: Thursday, June 17, 2004 4:45 PM
> To: How to use Revolution
> Subject: Pending messages
> 
> 
> Sort of the part 2 of my issues with "send"...
> 
> When "send in time" is used, the PendingMessages stores all 
> the current 
> messages waiting to be sent. However, if those messages have 
> parameters, you don't seem to be able to access those when reviewing 
> the PendingMessages, either with your own code, or with the message 
> box's "pending messages" panel.
> 
> in other words, sending
> 
> "myHandler first param, second param" (Which seems like a 
> pretty sloppy 
> syntax, BTW.)
> 
> shows up as "myHandler" in the pending message list.
> 
> If I have multiple scripts, calling the same handler, but with 
> different parameters, this can be difficult to sort one from 
> the next. 
> Is the "typical" technique for this to catch the message ID 
> when sent, 
> then register that with a "manager object" which can keep 
> track of all 
> the messages and related parameters based on ID information? 
> Now that I 
> write this, I'm assuming it is. But I'm open to any 
> suggestions or tips 
> from anyone who does this regularly.
> --
> Troy
> RPSystems, Ltd.
> http://www.rpsystems.net
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com 
> http://lists.runrev.com/mailman/listinfo/use-revolution
> 




More information about the use-livecode mailing list