[Etoys-notify] #6955 LOW Never A: "tile" morph embedded in a "ScriptingTileMorph"

[Zarro Boogs per Child]

#6955: "tile" morph embedded in a "ScriptingTileMorph"
-----------------------------+----------------------------------------------
  Reporter:  dmoco           |       Owner:  etoys         
      Type:  defect          |      Status:  new           
  Priority:  low             |   Milestone:  Never Assigned
 Component:  etoys-activity  |     Version:                
Resolution:                  |    Keywords:                
  Verified:  0               |    Blocking:                
 Blockedby:                  |  
-----------------------------+----------------------------------------------

Comment(by dmoco):

 Replying to [comment:2 ScottWallace]:
 > (1) Simply getting a tile for an object from its orange halo handle and
 dropping it on the desktop suffices to reproduce this phenomenon -- no
 need for the circumlocution of dropping it onto a project link, entering
 the other project, etc., which is only a red herring here.

 Yes, sorry for not checking this. As far as I remember I have only ever
 dropped a tile onto a script or a project view. The latter case is common
 for me because I typically experiment in one project and then move morphs
 to a new project if I want to preserved them.

 > (2) The phenomenon is not a bug.  For a variety of reasons, long ago it
 was determined to be appropriate to "wrap" any "naked tiles" sitting on
 the desktop in a neutral "holder".  This indeed does mean that if you want
 to get a halo on some inner structure within the tile holder, multiple
 halo-clicks may be required.

 Which differs from non-olpc versions of Squeak (although having just
 performed a test on 3.10 I realise EToys has other problems on that
 release). Can you tell me the rationale for the wrapping? An explanation
 may help me avoid reporting other non-bugs. Also is there is another more
 obvious way for transferring morphs between projects? I ask because if I
 struggled to figure out what was going on then surely others will.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6955#comment:4>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system