CirclesAndEllipses

[SabreBirdOne]

One thing I noticed when working on the copy constructor of Dragable class, if I were to stretch a Circle in the environment, realistically it becomes an Ellipse. Yet, those changes aren’t reflected in the internal state of the object - specifically the myShapeName field.

So I ended up pasting Circles after copying from Ellipses (internally they are still "circles"). This may happen vice versa. So I’m opening this new issue.

• When a circle is resized in certain ways, the Dragable should know that it is now an Ellipse.
• When an ellipse is resized in very precise manners, the Dragable should know that it is now a Circle. It is a niche corner case which must be addressed.

Comment: Honestly subtype polymorphism could have helped us so much here.

[SabreBirdOne]

Also, just how exactly does the team want ellipses to transform back into Circles? The only difference between circles and ellipses are their radiusX and radiusY fields: if radiusX equals radiusY, the Dragable is a circle, else the Dragable is an Ellipse. Users can turn circles into ellipses easily, but since the data are floating points, the user needs impractically high precision to get radiusX to equal radiusY and trigger the change from ellipse to circle.