Hi Lou,


you do not have to worry about re-drawing if you combine morphs only to create your application. That is, you write code that creates and configures line morphs, string morphs, rectangle morphs, and so on. If, however, you write your own #drawOn: methods, you have to tell Morphic about the side-effects that influence graphics via "self changed" or "self invalidRect: someRectangle". Yet, idiomatic use of Morphic means to employ custom #drawOn: methods _very_ scarcely.


In current Trunk, there are only 104 implementors of #drawOn: but 1051 senders of

#addMorph:, #addAllMorphs:, #addMorphBack:, #addMorphFront: combined.


Best,

Marcel


________________________________
From: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> on behalf of Bob Arning <arning315 at comcast.net>
Sent: Wednesday, December 27, 2017 3:56 PM
To: squeak-dev at lists.squeakfoundation.org
Subject: Re: [squeak-dev] Morph doesn't paint on every tick?


Well, there have been books and wikis and such, but I always prefer looking at the code itself.

On 12/27/17 9:43 AM, Louis LaBrunda wrote:

The whole mechanism of how morphs work, are drawn and such is a mystery to me.  I admit I
haven't looked very much but is there something I can read that will help me understand the big
picture of how morphs work?

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