[Etoys-notify] #6969 NORM Opportu: Textual Player Refs in Imported Morphs

Zarro Boogs per Child bugtracker at laptop.org
Fri May 9 06:02:47 EDT 2008


#6969: Textual Player Refs in Imported Morphs
-----------------------------+----------------------------------------------
  Reporter:  dmoco           |       Owner:  etoys      
      Type:  defect          |      Status:  new        
  Priority:  normal          |   Milestone:  Opportunity
 Component:  etoys-activity  |     Version:             
Resolution:                  |    Keywords:             
  Verified:  0               |    Blocking:             
 Blockedby:                  |  
-----------------------------+----------------------------------------------

Comment(by ScottWallace):

 Usually a project's referencePool has an object with internal name #Dot.
 (evaluate "ActiveWorld referencePool includesKey: #Dot to check).  Please
 try manually editing the textual script, substituting "Dot" for
 "Rectangle1", and see if you can accept the script in this form.  (In my
 image, duplicating your scenario, I *can* accept the script in this form.)

 If in fact the script with the Dot substitution can be accepted, whereas
 when you instead substitute "Rectangle2" in the same place you get the
 "Unknown variable: Rectangle2" error message when you try to submit the
 edited textual script, this proves that your Rectangle2 is not (yet) in
 the current project's reference pool, at least not with thge internal name
 #Rectangle2.  (And indeed in my image, after loading the morph, indeed
 there *is* no Rectangle2 in the reference pool.  Which is not surprising,
 since there are no references to it yet.  Once I "forced" there to be an
 entry in the referencePool for the loaded object, I was freely able able
 to edit the textual script, substituting Rectangle2 for Rectangle1, and to
 accept it without challenge, and with this edit the reloaded object
 worked...

 When you 'Discover from quick World based script that name is Rectangle2',
 exactly what did you do? I presume you wrote a tile script that referenced
 the new object, then looked at it textually to pick off the internal name?
 If you actually saw #Rectangle2 as the internal name used, in a
 demonstrably working script that referenced the object, it would be very
 surprising if Rectangle2 were not in the referencesPool...

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


More information about the Etoys-notify mailing list