[prev in list] [next in list] [prev in thread] [next in thread]
List: squeak-dev
Subject: Re: [squeak-dev] Morph doesn't paint on every tick?
From: "Taeumel, Marcel" <Marcel.Taeumel () hpi ! de>
Date: 2017-12-28 9:13:50
Message-ID: 1514452430917.15158 () hpi ! de
[Download RAW message or body]
Hi Lou,
you do not have to worry about re-drawing if you combine morphs only to cre=
ate your application. That is, you write code that creates and configures l=
ine morphs, string morphs, rectangle morphs, and so on. If, however, you wr=
ite your own #drawOn: methods, you have to tell Morphic about the side-effe=
cts that influence graphics via "self changed" or "self invalidRect: someRe=
ctangle". Yet, idiomatic use of Morphic means to employ custom #drawOn: met=
hods _very_ scarcely.
In current Trunk, there are only 104 implementors of #drawOn: but 1051 send=
ers of
#addMorph:, #addAllMorphs:, #addMorphBack:, #addMorphFront: combined.
Best,
Marcel
________________________________
From: Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> on behalf =
of Bob Arning <arning315@comcast.net>
Sent: Wednesday, December 27, 2017 3:56 PM
To: squeak-dev@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 m=
e understand the big
picture of how morphs work?
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} \
--></style> </head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hi Lou,</p>
<p><br>
</p>
<p>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.</p> <p><br>
</p>
<p>In current Trunk, there are only 104 implementors of #drawOn: but 1051 senders of
</p>
<p>#addMorph:, #addAllMorphs:, #addMorphBack:, #addMorphFront: combined.<br>
</p>
<p><br>
</p>
<p>Best,</p>
<p>Marcel</p>
<p><br>
</p>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, \
sans-serif" color="#000000"><b>From:</b> Squeak-dev \
<squeak-dev-bounces@lists.squeakfoundation.org> on behalf of Bob Arning \
<arning315@comcast.net><br> <b>Sent:</b> Wednesday, December 27, 2017 3:56 \
PM<br> <b>To:</b> squeak-dev@lists.squeakfoundation.org<br>
<b>Subject:</b> Re: [squeak-dev] Morph doesn't paint on every tick?</font>
<div> </div>
</div>
<div>
<p><font face="Georgia">Well, there have been books and wikis and such, but I always \
prefer looking at the code itself.</font><br> </p>
<br>
<div class="moz-cite-prefix">On 12/27/17 9:43 AM, Louis LaBrunda wrote:<br>
</div>
<blockquote type="cite">
<pre>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?</pre>
</blockquote>
<br>
</div>
</div>
</body>
</html>
[Attachment #4 (unknown)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic