Hi, Jerry,

Ah, yes, now I remember!

ScaleFactor works for every kind of morph *except* that it is broken, 
and has never worked, when it comes to PolygonMorph and its 
descendents.

The issue derives from the fact that Polygons (for their own good 
reasons) refuse to have "TransformationMorph" shells wrapped around 
them (a scaled polygon is itself just another polygon, after all,) 
and it's the TransformationMorph that holds the scaleFactor 
information.

Looking back I see that only last month I bumped into the very bug 
you reported, and after discussing the polygon situation within SC 
for a few rounds of email, I issued, in update 4465cleanups-sw dated 
29 October, a workaround for this problem -- see item 6 in the 
preamble to that update.

You should now see no more scaleFactor-related debuggers, and the 
scaleFactor of polygons is maintained at 1 -- that's the best we can 
do until someone does the work to implement a scaleFactor within 
PolygonMorph.

Cheers,

   -- Scott



At 1:07 PM -0800 11/28/01, Jerry Balzano wrote:
>Scott - Thanks for your response.  In the 3.2 Etoy system, either manually
>or from a script, the star, curve, and polygon all ignore attempts to set
>their scale factor, although (as I just found out) the ellipse, rect, and
>round rect behave just fine.  It must have been in 3.0 with the star
>specifically that I got the walkback error (from etoy system) I described
>in the previous message.
>				- Jerry
>
>
>At 12:49 PM -0800 11/28/01, Scott Wallace wrote:
>>Hi, Jerry,
>>
>>Please say more about how this error happened.  How did you "try to
>>set the scaleFactor..."?
>>
>>Was it through a viewer or tile scriptor in the etoy system?
>>
>>I've just tried setting scaleFactors manually (from an etoy viewer)
>>and programatically (from an etoy scriptor) for various objects in a
>>3.2a system and all appeared to be well.
>>
>>
>>At 11:11 AM -0800 11/28/01, Jerry Balzano wrote:
>>>If you try to set the scaleFactor of a morph (or should I say morph's
>>>player?), I get a walkback window headed "MessageNotUnderstood: scale:".  I
>  >>first discovered this using v3.2a, but the problem also appears in v3.0.
>  >>