problem waiting - spellchecker

Lynch, Jonathan bnz2 at cdc.gov
Thu Sep 1 11:34:32 CDT 2005


I know I am asking an ignorant question here, but...

Is there no way to accomplish your goal by using a modal stack for user
input? This would automatically block the user from doing anything else
until the modal stack is closed.

-----Original Message-----
From: use-revolution-bounces at lists.runrev.com
[mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of MisterX
Sent: Thursday, September 01, 2005 12:20 PM
To: 'How to use Revolution'
Subject: RE: problem waiting - spellchecker

Dave,

After some logical thoughts, this wouldn't work. Maybe it could... But
is it
"realistic" to make a simple process more complicated?

repeat... 
  ...
  put "wait" into xosdictionary["current"]
  --put the waitdepth -- always 1
  --if the waitdepth < 2 then
    wait until xosdictionary["current"] = "continue" with messages
  -- else skip... poor idea...
  --end if
  ...
end repeat
then, any button in the spellchecker GUI will do something like ignore,
fix,
etc... and then
  ...
  put "continue" into xosdictionary["current"]
end mouseup

The reason the wait is in the first place is to wait for the user input
(or
abort). Since it's blocked, the only way this could work (it's in a loop
that parses each word) would be if i added a double condition with a
property reset and that gets messy... 

This requires major code change (not again, 2 already)... 

Why can't this wait statement work each time it is called?
If it works 2 or 3 times why not 4 or more?

What can affect this? 

Im removing now all outside influences for the next test run...

The question remains, why does it lock up?

i do have an alternate callback algorithm that might work but im not to
fond
of it's obscure ways... "wait" was so simple...

At least, i got a "good" word parser now... Dictionary is learning and
learning (so am i). And i got a way to update "styled" text being
corrected
too :)

cheers and thanks for the help
Xavier
http://monsieurx.com

> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com 
> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of 
> David Burgun
> Sent: Thursday, September 01, 2005 14:11
> To: How to use Revolution
> Subject: Re: problem waiting - spellchecker
> 
> Hi,
> 
> Just at thought, but could you do something like this:
> 
> In handler that you want to wait in:
> 
> global gConditionFlag
> 
> 
> put false into gConditionFlag
> send CheckIfDone to this card in 10 ticks -- or a good value 
> for the task
> 
> global gConditionFlag
> 
> on CheckIfDone
> if gConditionFlag = false then
> send CheckIfDone to me in 10 ticks -- or a good value for the 
> task exit CheckIfD end if
> 
> --
> -- Do the update
> --
> 
> end CheckIfDone
> 
> not sure how this would fit into your project though.
> 
> All the Best
> Dave
> 
> >Hi everyone
> >
> >I've advanced quite a lot in the spell checker BUT
> >
> >the wait until [condition] with messages
> >
> >still gives me lots of troubles.
> >
> >It works usually the first time, maybe a second time, but it 
> definitely 
> >locks up after 2-4 loops...
> >
> >By locking up, i mean that it doesn't seem to get either the "with 
> >messages" or that the condition is correct.
> >
> >I checked if the waitdepth is not > 1 but it is not. And if 
> it was, how 
> >do you delete the pending waits? grrr...
> >
> >After a control-C to abort the "wait", the error message 
> indicates that 
> >the lock up happens at the "wait" statement.
> >
> >What can cause this problem? Nothing else is running or 
> being sent or 
> >listed in the pending messages...
> >
> >This is far from reliable "at all" from what i can tell. Even if i 
> >debug (usually forces things to work better - or worse ;), 
> it doesn't 
> >help. I see no cause for the wait to "hang"...
> >
> >Thanks for any help on this...
> >
> >Other than that, i got a "real" word parser going, and i'll be also 
> >putting back the style to the corrected words where 
> necessary... This 
> >is quite a challenging application - to be done the right way ;)
> >
> >cheers
> >Xavier
> >
> >
> >-----------------------------------------
> >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
> >_______________________________________________
> >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
> 
> _______________________________________________
> 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

_______________________________________________
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





More information about the use-livecode mailing list