problem waiting - spellchecker

[xbury.cs at clearstream.com]

im using 2.6...

And it is missing the "condition"...

cheers
Xavier

use-revolution-bounces at lists.runrev.com wrote on 30/08/2005 10:21:16:

> 
> On 30 Aug 2005, at 08:18, xbury.cs at clearstream.com wrote:
> 
> > Superb!!!
> >
> > Thanks all for your great help!!!
> >
> > We got a spellchecker almost working...
> >
> > The revDocs need help here!!! It sure wasn't clear at all...
> >
> > wait [for] number [seconds | ticks | milliseconds] [with messages]
> >
> > doesn't imply that you can add a condition to wait for! Only time...
> >
> > Where i was confused is that this looked like a
> >
> >   read from socket IP with message "whatever"
> 
> What version of Rev are you using? The current docs show these syntax 
> descriptions:
> 
>    wait {until | while} condition [with messages]
>    wait [for] number [seconds | ticks | milliseconds] [with messages]
>    wait for messages
> 
> But I seem to remember in earlier versions that the "condition" 
> version wasn't listed.
> 
> Cheers
> Dave
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution



-----------------------------------------
Visit us at http://www.clearstream.com
                                                          
IMPORTANT MESSAGE

Internet communications are not secure and therefore Clearstream
International does not accept legal responsibility for the contents of
this message.

The information contained in this e-mail is confidential and may be
legally privileged. It is intended solely for the addressee. If you are
not the intended recipient, any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful. Any views expressed in this e-mail are
those of the individual sender, except where the sender specifically
states them to be the views of Clearstream International or of any of
its affiliates or subsidiaries.

END OF DISCLAIMER