Collision will not work correctly when having objects in a container that is rescaled

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Put your display objects in a container object.
2. Increase the scale (or size) of the container object.
3. Do collision detection on the objects in the container.

What is the expected output? What do you see instead?
The expected output is to see that the collision detection adapts to the
rescaled sizes. Instead the collision works only on the checked objects
original sizes, before rescaling.

What version of the product are you using? On what operating system?

Please provide any additional information below.
attaching a sample file that shows how this behavior occurs. Grab any
circle in the sample to rescale the container. Make them collide and
observe that as they grow collision is not detected in the outer parts of
the circle.

Original issue reported on code.google.com by jorgen.b...@gmail.com on 31 Mar 2009 at 12:30

Attachments:

• scale_container_bug.zip

[GoogleCodeExporter]

Yup, it doesn't account for transformations made to parents.  When I get around 
to 
pushing out an update to the CDK, I'll be sure to include a routine to run 
through 
any/all parents and include their transformations prior to snagging the display 
objects for collision detection.

Original comment by lessthan...@gmail.com on 31 Mar 2009 at 6:06

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This problem has been addressed in the latest release, version 1.5

You can now do whatever you see fit to parent containers without issue. 
Download and
enjoy! :D

Original comment by lessthan...@gmail.com on 7 Jun 2009 at 12:03

• Changed state: Done