<body><div id="__MailbirdStyleContent" style="font-size: 12pt;font-family: calibri;color: #000000">
If a morph needs a world from somehwere without being in a world, then something is fishy. :) Usually, a caller will provide a world for that morph such as in #openInWorld: or #intoWorld:. After that, "self world" will not be "nil" anymore.<div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 12.11.2017 16:54:30 schrieb Bob Arning <arning315@comcast.net>:</p>
<p><span style="font-family: Georgia">One caveat is that "self world" for a Morph
will answer nil if the morph is not currently *in* a world.</span><br>
</p>
<br>
<div class="moz-cite-prefix">On 11/12/17 10:11 AM, David T. Lewis
wrote:<br>
</div>
<blockquote type="cite" cite="mid:20171112151107.GA36156@shell.msen.com">
<pre wrap="">The "self world" expression works for morphs, and certainly it is easier to read.
It may be somewhat slower, although that would not be a concern in most usages.
My main concern is correctness, because failures in this area can hang up the
UI entirely, and errors are difficult to debug.
When transitioning from one project to another the World variable is set to
the new project's world in #finalEnterActions:. Thus the World global is a
shortcut reference to the world of the current project, and that is what leads
me to suggest the expression "Project current world".</pre>
</blockquote>
<br>
</blockquote>
</div></body>