FMSLogo Code

Relabel the inputs of ELLIPSEARC2 to match the documentation.
This brought to light the apparent mislabelling of x as y and vice-versa that had confused me before. I'm confident in the naming of the inputs, but not as much in the naming of the local variables.

The good news is that, even if the variable names are incorrect, the procedure still passes all tests.

Replace usage of ELIPSA2 with ARCOELIPSE2
ELIPSA2 is deprecated and ARCOELIPSE2 is the preferred name.

Add a regression test for a degenerate case of ELLIPSEARC2
x-semiaxis = 0 and the angle swept is only 10.

Remove trailing whitespace

Improve the dashed-line ellipse example for ELLIPSEARC2
- Don't draw the ellipse twice
- End with the pen state down

esta -> ésta to avoid ambiguity

Rename :principio.ángulo to :ángulo.de.partida
The new name feels like a more natural translation for "start.angle"

Update the documentation for ELLIPSEARC2 to match fix for Bug #494.

Fix the documented order of the X and Y inputs for ELLIPSEARC2.
The last time I looked at ELLISEARC2, I had convinced myself that the order was swapped, but taking a closer look at the ELLIPSEARC2 behavior, I realize that I was wrong (or at least I was wrong the way these inputs are documented).

This is good news, because X Y makes more sense than Y X.

Finish fixing Bug #494; ELLIPSEARC2 now leaves at the point where the ellipse stopped.

This updates ELILPSEARC to account for the fix to ELLIPSEARC that makes it correctly honor the angle.