Screen saver does not have full parity with main environment
A Logo programming environment for Microsoft Windows
Brought to you by:
david_costanzo
Menu
▾
▴
#373 Screen saver does not have full parity with main environment
There are many primitives which the main environment supports that are not supported by the screen saver. For example, the networking and windowing API is not supported. While these may not be necessary for the target screen saver programs, this work will be necessary for the wxWidget port, so it might as well be done for the screen saver.
In FMSLogo 7.0.0, the screen saver is built with wxWidgets so it has nearly complete parity with the main environment. As of now, it's missing a few commands that would be dangerous (creating a dialog box that would be hidden behind the window), as well as procedures related to the commander and scrolling are no-ops (for example, CLEARTEXT doesn't have much meaning when there's no commander).
It turns out that the wxWidgets port was completed far before these primitives were added to the screensaver, and it wasn't until I ported the screensaver to use wxWidgets that they could be used. As of FMSLogo 7.0.0, the screensaver will support all of the commands that the main environment supports, even ones that aren't particularly useful, like DIALOGFILEOPEN.
Some commands make no sense in a screensaver. For example CLEARTEXT assumes that the commander exists, but the screensaver doesn't have a commander. These commands are implemented as no-ops so that programs which run such commands won't throw errors when used as a screensaver.