FMSLogo Code

Update the translation tables in preparation for the 7.0.0 release.

Fix a recent regression that stopped the Del key from working in the workspace editor.

Fix a regression from 6.35.0 where items in the context menu from the minieditor and from the command input when the commander is undocked did not get disabled when selecting them does nothing.

In wxWidgets, the OnUpdate* don't fire when a context menu is displayed from a wxDialog, so the code now enables/disables each item before showing the context menu.

Fix a regression from 6.35.0 where keyboard shortcuts like Ctrl+C and Ctrl+V did not work in the minieditor. The problem is that these must no be added to an accelerator table. Rather than add this to CMiniEditor, this revision follows the pattern for CCommanderInput, creating the accelerator on the subclass of CLogoTextCtrl.

Fix a problem in BITBLOCKTEST.SMOKETEST where, depending on where the turtle was, it would do the BITLBLOCK in a different location, which would make the screenshot comparison fail. Now the test runs CLEARSCREEN to enforce that the turtle is always in the same location.

Update the expected test log after a recent test run.

Fix bug #486; The turtle can now walk along the screen extents in FENCE mode.

The problem was that if you tried to walk along the extents, due to the impercision of floating point arithemetic, you might end up crossing the extent by 1e-14 or something similarly small (especially after conversion from degress to radians).

My fix was to permit the same "rounding" tolerance that POS uses when showing the true turtle position. My thinking is that this tolerance is used to mask very small amounts of user-facing of imprecision that are the turtle's position, the screen extent is another user-facing boundary, so it should use the same precision.

Fix a regression that broke SETPIXEL on windows (that is, it made it as bad as it on GTK3). The problem was a typo in the "__WXMSW__" conditional compilation.

Refactoring: Add comments to wrap_* functions.
Replace > operations with equivalent < operations.

Work around a wxWidgets bug where wxDC::DrawPoint() draws two
pixels under GTK3. On this platform, a zero-pixel line is drawn
instead. This is not quite correct and causes some anti-aliasing
which bleeds into the pixel, but it's better than before.