<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Georgia">The setting and later reporting of position
are not different and this is a cause of occasional errors. If
you have</font></p>
<p><font face="Georgia">MorphA>>initialize</font></p>
<p><font face="Georgia"> self addMorph: (MorphB new position:
1@1)</font></p>
<p><font face="Georgia"><br>
</font></p>
<p><font face="Georgia">then B will be positioned one pixel from the
top left of A. If, however, you do</font></p>
<p><font face="Georgia"> self addMorph: (MorphB new position:
1@1)</font></p>
<p><font face="Georgia">sometime later after A has been added to the
World and possibly moved, then you may get something different,
like B being one pixel from the Display top left, regardless of
where A is currently. If that is the case, and, maybe, as a
general precaution, then<br>
</font></p>
<br>
<p><font face="Georgia"> self addMorph: (MorphB new position: 1@1
+ self position)</font></p>
<p><font face="Georgia">would be more robust.<br>
</font></p>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/19/17 11:41 AM, Louis LaBrunda
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:m1ei3dd621tii1i6cihefs76no3hnefi9p@4ax.com">
<pre wrap="">It seems odd to me that when the position of a new TransformationMorph is set it is based on
where it is to go in its parent morph but if you ask it its position later, it answers its
position on the screen. I say that this disconnection may have something to do with the
rotation problem because I think the rotation code does some math based upon the position of
the morph. I expect the code thinks it is using a position based upon the parent and not the
screen.
</pre>
</blockquote>
<br>
</body>
</html>