Chris Muller-3 wrote
> Okay, that's fine, my broader point just wondering whether that
> existing mechanism is sufficient for Marcel's multi-Process situation,
> or whether there really is a need to introduce yet another one into
> Morphic.
> 
> We know it has to be syncrhonized anyway at the bottom, right? -- its
> not going to be multitasking in multiple drawing primitives
> simultaneously, the synchronization must occur at a higher level, and
> there is an existing higher-level mechanism to do that..
> 
> On Wed, Aug 24, 2016 at 4:39 PM, David T. Lewis <

> lewis at .msen

> > wrote:
>> On Wed, Aug 24, 2016 at 11:21:39AM -0500, Chris Muller wrote:
>>> Hi Marcel, if you are talking about introducing some kind of code to
>>> guard against someone mis-using Morphic, then, yes, it *is* a relevant
>>> point ot the discussion.  You can render your image just as unusable
>>> with
>>>
>>>     String new become: nil
>>>
>>> but we don't want to guard against that..   If Etoys or Kedama are
>>> doing that, shouldn't they be changed to use WorldState
>>> addDeferredUIMessage:?  That's the SharedQueue designed to let apps
>>> with background processes append operations to be handled by the UI
>>> Process..
>>
>> It is good style to use Project current addDeferredUIMessage: rather
>> than WorldState addDeferredUIMessage:
>>
>> Of course we are talking about Morphic here, but still ...
>>
>> Dave
>>
>>

Okay, that just leaves the job to an additional watcher process. Self did
that, too.

Best,
Marcel



--
View this message in context: http://forum.world.st/Using-Semaphores-in-drawing-code-tp4912213p4912551.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.