<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Hi,<br></div><div><br></div><div>I instantiated a new instance of the class Morph and opened in the word and tried to move it with the move morphic halo handle. The mophic halo moves alongside the HandMorph but the Morph instance doesn't. The pick up handle doesn't do anything visible. The message openInHand doesn't work, at least seemingly. <br></div><div><br></div><blockquote type="cite"><div>Subclass PlacedMorph defines a local coordinate system (see its class comment). Morphs NOT in the PlacedMorph hierarchy live in the space defined by their owner. Their local coordinate system is the same as the owner's. They ignore #morphPosition:.<br></div></blockquote><div><br></div><div>Is this behavior a side effect of the fact that Morph ignores #morphPosition:? If it is, maybe some animation, visual feedback would be nice to keep Morphic's directness principle intact. <br></div><blockquote type="cite"><div>The user quickly realizes that everything on the screen is<br></div><div>a morph that can be touched and manipulated.<br></div><div>Compound morphs can be disassembled and individual<br></div><div>morphs can be inspected, browsed, and changed. Since<br></div><div>all these actions begin by pointing directly at the morph<br></div><div>in question, we sometimes say that directness is another<br></div><div>morphic design principle. Concreteness and directness<br></div><div>create a strong sense of confidence and empowerment;<br></div><div>users quickly gain the ability to reason about morphs the<br></div><div>same way they do about physical objects.<br></div><div><br></div><div>An Introduction to Morphic: The Squeak User Interface Framework (John Maloney)</div></blockquote><div><br></div><div>Regards,<br></div><div>Szabolcs<br></div></body></html>