(1094) Crash when entering LSL code that wrapped to another line:
This problem occurred when typing in code that starts to wrap to another line when using of one of the "grid" code editors where line wrapping is enabled such as the LSL Action Wizard, State Variable & Functions Editor, State Variable Configure Options editor & the Edit User LSL Actions editor. It did not occur in the other standard editors (State Entry/Exit Action, Transition Action, etc). This has been fixed.
(1074) Code Completion didn't work on wrapped code lines:
Code Completion did not work when using of one of the "grid" code editors where line wrapping is enabled such as the LSL Action Wizard, State Variable & Functions Editor, State Variable Configure Options editor & the Edit User LSL Actions editor. This has been fixed.
(1089) MOAB hang on code completion:
MOAB could hang when selecting a code completion item in a word-wrapped code editor (e.g., State Variable Initial Value field in the State Variable & Functions Editor). This has been fixed.
(1095) MOAB crash on entering State Variable Initial Value field:
In the State Variables & Functions Editor, a program abort would occur if a value was inserted into the Initial Value field of a State Variable before its Name field was assigned. This has been fixed.
(1099) State Variable Initial Value field not parsed on tab:
Tabbing out of the Initial Value field of a State Variable (State Variables & Functions editor), would not always check the code for errors. This has been fixed.
(1100) State Variable Initial Value field opened with completion list box:
Clicking in a set Initial Value field of a State Variable (State Variables & Functions editor), would open the Code Completion list box. This has been corrected.
(1101) Selecting item from Completion List Box reset cursor position to start
For grid code editors (e.g., Initial Value field in the State Variables & Functions editor), clicking on an item within the Completion List Box, would incorrectly reposition the cursor to the beginning of the editor. This has been fixed.
(405) Can't close a State Variables and Functions Editor containing an invalid field:
If there is a field with invalid data in the State Variables/Functions Editor, the editor cannot be closed using the ESC key. It will also not close using the Close Box the first time it is pressed. In this case the Cancel button should be used to abort the changes.
(224) Crash on startup updating Splash Screen:
Particularly in Windows 7 installations a rare crash may occur on startup of the MiceOnABeam program after displaying the initial Splash Screen. Code has been put in to detect this issue and avoid aborting the program.
A work-around for the problem if it still occurs is to disable the Splash Screen by de-selecting Show Splash Screen in the General pane of the Tools/Options menu.
(1032) Functions cannot be defined within Compiler Directives within Custom Globals:
Incorrect parsing errors will be flagged if a function is declared within Compiler Directives (such as #if...#endif) within the Custom Globals LSL code entered for a model. Assuming a correct function definition, these parsing errors can be ignored and the function will be properly included in the generated code.
(1096) Entering an escaped slash right before terminating quote causes parsing error:
Within a string constant, entering an escaped slash right before the terminating quote will cause a parsing error. To avoid the error message insert another character just before the right quote, such as a blank; i.e., llOwnerSay("\\explode\\ ");