RE: The Wait command

2011-06-24 Thread Ralph DiMola
v.com] On Behalf Of John Craig Sent: Friday, June 24, 2011 5:07 PM To: How to use LiveCode Subject: Re: The Wait command This works for what I understand the original scenario was. If you click button 1, it waits either until the 10 seconds has elapsed or until button 2 is pressed. :) Add

RE: The Wait command

2011-06-24 Thread Ralph DiMola
nt: Friday, June 24, 2011 5:07 PM To: How to use LiveCode Subject: Re: The Wait command This works for what I understand the original scenario was. If you click button 1, it waits either until the 10 seconds has elapsed or until button 2 is pressed. :) Add 2 buttons to a new stack; 1st but

Re: The Wait command

2011-06-24 Thread J. Landman Gay
On 6/24/11 3:52 PM, Bob Sneidar wrote: See this is the perfect example of why some kind of multiple processing thing is needed. If you say wait until then no other processing can take place. The OP specifically wanted to block all other processes, so in this case "wait" is a good solution.

Re: The Wait command

2011-06-24 Thread Pete
Hi Bob, This is definitely new territory for me but I think perhaps the "with messages" option of the wait command does what you want. The dictionary indicates that "with messages" allows the user to carry on doing other things in LC while it is waiting for suspended handler to to resume. Pete Mol

Re: The Wait command

2011-06-24 Thread Pete
I didn't get that from the dictionary entry for wait, although I guess everything after "until" is just a compound condition. Never thought of that, thanks for the idea. Pete Molly's Revenge On Fri, Jun 24, 2011 at 1:53 PM, J. Landman Gay wrote: > On 6/24/11 2:

Re: The Wait command

2011-06-24 Thread John Craig
This works for what I understand the original scenario was. If you click button 1, it waits either until the 10 seconds has elapsed or until button 2 is pressed. :) Add 2 buttons to a new stack; 1st button script; on mouseUp set the uFlag of this card to false put the millisecs + 1000

Re: The Wait command

2011-06-24 Thread Pete
Thanks - sounds like this is trivial. Wouldn't it be nice though if the wait command could do "wait until or " Pete Molly's Revenge On Fri, Jun 24, 2011 at 1:26 PM, John Craig wrote: > Try something like; > > Put the millisecs + 5000 into tTime > Repeat until

Re: The Wait command

2011-06-24 Thread J. Landman Gay
On 6/24/11 2:58 PM, Pete wrote: Trying to figure out how to suspend processing until either a condition is true OR a specific amount of time has elapsed. Looks like the wait command allows one or the other but not both. Any ideas how to do this? You can use both in a wait command, for example

Re: The Wait command

2011-06-24 Thread Bob Sneidar
See this is the perfect example of why some kind of multiple processing thing is needed. If you say wait until then no other processing can take place. Even in the repeat loop it doesn't help. If the condition is triggered by some kind of execution the even will never happen because you are wa

Re: The Wait command

2011-06-24 Thread John Craig
Try something like; Put the millisecs + 5000 into tTime Repeat until the millisecs > tTime or the uFlag of this card = true Wait for 100 millisecs with messages End repeat Sent from my iPhone On 24 Jun 2011, at 20:58, Pete wrote: > Trying to figure out how to suspend processing until either a

Re: The Wait command

2011-06-24 Thread Mark Schonewille
Hi Pete, There are so many way to do what you want that the following is bound to look silly. local lTimer,lCondition on foo theSeconds if the seconds - theSeconds >= lTimer and lCondition is true then -- do something here else send "foo theSeconds" to me in 1 sec end if end foo