Maybe for a 5' experiment is well :).

But World doOneCycle do handle events also, not just rendering, what should lead to a wrong state :).� I don't forbid anybody to use it, just tell him to think about it :P.

On Thu, Jun 21, 2012 at 4:13 PM, Stefan Marr <smalltalk@stefan-marr.de> wrote:
Hi:

On 21 Jun 2012, at 15:57, Guillermo Polito wrote:

> I bet there is a Morphic API that allows you to process the next drawing request.
>
> Hmm, that sounds like forcing the framework... I think that having a second process is the right way...

For an experiment? Getting the concurrency right in a second process sound a lot less appealing than using `World doOneCycle`, which seems to be used in other places for the same purpose as well:

MorphicUIManager>>#spawnNewProcess
� � � �UIProcess := [
� � � � � � � �[World doOneCycle. �Processor yield. �false] whileFalse: [].
� � � �] newProcess priority: Processor userSchedulingPriority.
� � � �UIProcess resume

Best regards
Stefan


--
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 2974
Fax: � +32 2 629 3525