It seems that the getters and setters for the height are all botched up when the DisplayObject has any rotation applied to it at all.
The getter for the height returns the total height of all the bounds.
The setter for the height sets the height regardless of rotation.
If you set the same value for height several times in a row, you will get about 3 different results until it stays at the same result.
If the heigt’s getters and setters are different, imagine the ramaflacations involved, first and foremost setting properties via “+=”.
Just posted up a quick example:
(ZIP with SWF is attached - FLA can be made available upon request)
The properties “width”, “height”, and “rotation” are applied in that order as listed, but setting them in a different order will affect the result differently, but I don’t have the time for that.
Anyone else annoyed by this? Whatever happened to the Logic?
I’m still waiting for properties (in progress by me) such as “unscaledHeight”, and sprites which do not stretch when you set the height or width.
