BITCUT, BITPASTE, and BITPASTETOINDEX display a modal message box and throw a stop error when they fail (either due to bad input, a bad state for the instruction, or memory constraints).
This is inconsistent with how the rest of the procedures behave, so it should be corrected.
I have reproduced this in FMSLogo 7.7.0, but the behavior has existed since at least MSWLogo 6.5b.
How Reproducible:
Every Time
Steps to Reproduce:
1) Start a new instance of FMSLogo
2) Run SETBITINDEX 1 BITPASTE
What Happens:
You see a dialog box that says "Nothing to Paste", then the commander prints "Stopping...", which indicates that a stop error was thrown.
Expected Result:
FMSLogo does not display a message box. Instead it throws an error that is specific to the problem.
This is fixed by [5450]. The fix will be available in FMSLogo 8.0.0.
Along these lines, if BITMAPTURTLE is called and there is no bitmap at the corresponding index, then FMSLogo will print an error to the commander's history box instead of showing a modal dialog box about it.