On 18-feb-2007, at 21:58, Eric Y. Kow wrote: > Hi, > > On Mon, Feb 05, 2007 at 16:17:41 -0000, José Miguel Vilaça wrote: >> In theory this seems the solution but when I tested it I find out >> that it >> doesn’t. The very long computation gets the attention of the >> processor and >> blocks the graphical interface; clicking the Stop button don’t >> fire the >> actions. > > Does calling wxcAppSafeYield in your long computation (look in the > index > of the API) help? I don't actually know the answer, just making some > guesses. You might want to look into what Dazzle/XTC do, otherwise.
Just as a heads-up: Dazzle doesn't solve this problem at all. Long computations are split in parts, the (lazy) evaluation of which is driven from the UI, but any truly long evaluation will still block the UI. Doei, Arthur. -- /\ / | [EMAIL PROTECTED] | Work like you don't need the money /__\ / | A friend is someone with whom | Love like you have never been hurt / \/__ | you can dare to be yourself | Dance like there's nobody watching ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ wxhaskell-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
