Hi, there.

The subscribe/update-code for our system change notifier is NOT in place for CodeHolder and its subclasses. That would be a first step. "step" ... ha ha ... :-)

I suppose that this stepping is not related to morph updates in general but only to ToolBuilder and SystemWindow. If you take a look at #updatablePanes, you can trace it.

Please do not confuse this issue with re-drawing. Morphic does not tick to draw. Only our pluggable widgets that are requested to update their contents frequently might trigger a re-draw --- but only if contents change. ;-)

Best,
Marcel
Am 21.01.2018 21:25:03 schrieb David T. Lewis <lewis at mail.msen.com>:
On Sun, Jan 21, 2018 at 09:08:32PM +0100, St??phane Rollandin wrote:
> >If it is true that the stepping updates are being done primarily to ensure
> >updates for all browsers within a Morphic world, and if it is also true
> >that some sort of registry is required, then it might make sense for the
> >current world to be responsible for keeping the registry, such that change
> >notifications would be delivered to browsers within the current world, and
> >not to all browsers in all of the other Morphic projects that may exist
> >in an image.
> It is common for me to have browsers open on the same class across
> different projects, so I would appreciate if all browsers were updated.
>
> Actually, I have already be bitten by old code still being displayed as
> current in a browser. I do not remember the details though, but it could
> involve swapping projects.

Stef,

Of course you are right, they do all need to be updated. Sorry that was
a bad idea, please disregard.

Dave


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180122/5d29b056/attachment.html>