On Wed, Jan 28, 2015 at 11:31 PM, Laura Risani <laura.risani@gmail.com> wrote:Hi��Ben ,#fork let me implement the overall functionality i wanted, but i had to introduce some minor changes into the design to reflect the concurrent nature of the msg. So i still feel curious about how one could implement this msgWaiting>> wait : seconds"i take the flow control during 'seconds' without halting image morphs and only then return to the sender "There is only one Morphic UI loop process which repetitively cycles for Morph stepping and the main interactive UI.�� Use "Tools > Process Browser" to take a look at that process (priority=40) and its stack and you'll WorldMorph>>doOnceCycle.�� If you are curious, you can put a "self haltOnce" in that method and invoke it using ��"System > Enable halt/inspect once" and it will spawn that fault in that cycle off to another process you can trace through, while the main process continues to cycle.However if you perform a non-concurrent #wait or busy calculation, then the UI loop is prevented from looping at its usual speed (see #interCyclePause).cheers -ben��Best,LauraOn Tue, Jan 27, 2015 at 7:00 PM, Ben Coman <btc@openinworld.com> wrote:Hi Laura, Can you provide some more context by pasting code for how you expect both your UI and calculation methods to interact? What is the application?cheers -benOn Wed, Jan 28, 2015 at 5:49 AM, Laura Risani <laura.risani@gmail.com> wrote:Hi all,Thank you for your answers.But i yet can't see how to implement the method i wanted, because #fork schedules the process and immediately returns but i'd like to wait and only then return the answer.Best,LauraOn Tue, Jan 27, 2015 at 3:46 PM, Laura Risani <laura.risani@gmail.com> wrote:Hi all,I need an object/method like this oneWaiting>> wait : seconds"i take the flow control during 'seconds' without halting image morphs stepping/handling (as Delay>>wait: does) and then return to the sender "How can i��implement it?Where can i borrow for reuse an existing one from?Best,Laura