On 05.11.2010, at 23:18, Sean P. DeNigris wrote: > > In the process of my app's execution, it needs to put up a UI, and pause > until the UI returns an object (only this piece of code needs to pause, the > rest of the world can keep going). I was thinking of using forks, but > FillInTheBlankMorph seems to manually drive the world's doOneCycle while it > waits (seems ugly and a little too controlling). > > What would be the best way?
Redesign your app so it does not have to pause but is event-driven (or possibly continuation-based). Then just lock the part that should not be interactive. FillInTheBlank has to do that ugly doOneCycle because it was made to work with non-eventdriven programs. - Bert - _______________________________________________ Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners
