This page contains texts snippets which could go to the FAQ but are not yet edited. Don't hesitate to do it if you like...
Date: Mon, 21 Aug 2000 13:38:54 -0400 (EDT)
From: Bob Arning
Subject: Re: Need help on Morphic
Hi Stephane,
On Mon, 21 Aug 2000 17:57:24 +0200 (MET DST) Stephane Ducasse = wrote:
>Question 1: How to forbid halos
If what you mean is you don't want a particular morph to have halos =
when cmd-clicked, then implement
wantsHaloFromClick
^ false
for that morph, but be careful as that may make it harder to debug or =
delete that morph.
>Question 3 More a remark. I was thinking that delete just remove the =
morph
>from the world, and was wondering what is the opposite action that =
could bring
>the morph in the world. I tried openInWorld and it works but I was =
thinking
>that the protocol could be more symmetric.
The symmetry is missing, I suppose, because #delete works in all cases =
to break the owner<->submorph relationship. Adding something to the =
world, on the other hand, has a huge number of possibilities: which =
existing morph you wish to be the owner of the new morph and where =
(first, last, other..) the new morph should be positioned relative to =
any existing submorphs of the new owner.
>Question 5 Is caseOf: really used?
It doesn't appear to be used in the image, but perhaps some folks use =
it in private fileins.
Update: As of 3.1alpha, it seems to be used in a few methods, but you have to find it by searching source, since it's inlined and a standard "senders of..." search won't find it. - RandalSchwartz