(1315) Size of Transition Editor increased for new experience permission events:
The size of the Transition Editor has been increased to accomodate the new experience permission events
(1106) Event data now cleared after processing the event:
In the generated code, the event argument data is automatically saved in the global variable EventData every time an event is received. To save memory, the EventData variable is now cleared at the end of processing of each event.
(1336) LSL lines can now be selected by clicking on line numbers:
Within an LSL Code Editor, a line of code can now be fully selected by simply clicking on its line number. Multiple lines of code can be selected by clicking down, dragging the mouse cursor across the range of line numbers to be selected and then releasing the mouse button. Shift-clicking over a line number, will extend the selection to the corresponding line.
(1330) Additional validations for incomplete models:
Additional checks for incomplete models are now done and warnings are issued for these when the LSL code is generated.
In particular checks are now done for:
- Missing incoming transition for State, Final State, Shallow/Deep History Point or Terminate Point;
- Missing incoming or outgoing transition for Choice Point or Junction Point;
- Originating transition with undefined event;
- Missing Initial Transition for a Composite State;
(1314) New Events:
New & Updated LSL Actions:
Updated LSL Actions:
- (1127) HTTPRequest: Corrected prompt for Body parm in HTTPRequest.
- (1134) GetSeatedAvatar: Corrected prompt for GetSeatedAvatar.
- (1135) ScanForSomething & ScanRepeatedly: Added options to scan for stationary scripted objects to ScanForSomething & ScanRepeatedly LSL Actions;
(1309) New LSL functions and constants:
The following new LSL functions and constants are now supported. Note that some of them may still be in pre-release status in Second Life and as such may not yet be fully-supported.
(1080) An integer State Variable could be assigned a float value in initialization:
The initialization of an integer variable within the State Variables and Functions Editor and within the Custom Globals code editor, could be assigned a float value that would not be flagged as a coding error. This has been fixed.
(1332) Shift click to extend code selection to the left did not work:
You can now shift-click to the left of an existing LSL code selection and the selection will be expanded to that point.
(1344) Crash in State Variables & Functions Editor when variable name not set:
Selecting a code completion list box item via the mouse for a new, yet unnamed state variable, within its initialization code, could cause a crash to occur. This has been fixed.
(1128) Selecting a State Function could open a Code Completion list box:
Selecting an existing State Function would open a Code Completion list box if the first line of the function was not a comment. This has been fixed and no longer occurs.
(1131) LSL code selection from right to left omitted closing bracket:
Positioning the cursor just after a bracket followed by a click and drag left, did not include the closing bracket in the selection. This has been fixed.
(1149) Tabbing LSL code left when whole lines were selected could tab non-selected lines:
This has been fixed. Note that all lines being tabbed will now be fully selected.
(1329) Undoing move of outgoing transition source to Junction Point didn't restore Guard Condition:
This has been fixed.
(1347) Tabbing left one or more selected lines that include a blank line caused a Code Editor error:
Attempting to tab an empty code line left caused a (recoverable) LSL Code Editor error. This has been fixed.
(1348) Tabbing code lines could sometimes cause a scroll jitter:
This has been fixed.
(1148) Error in help pop up for llTriggerSoundLimited:
Help text corrected.
(1148) Tabbing lines of code that included ERR lines produced incorrect results:
If LSL error lines are included in a code selection, then tabbing will be disabled for that selection.
(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:
The parser will report an error if there is an escaped slash inserted into a string right before the terminating quote. The error message can be safely ignored. To avoid the error message insert another character just before the right quote, such as a blank.
(1071) DPI Scaling may distort various dialogs:
If the DPI Scaling is set at a value other than 100% (Windows Display control panel), then various MiceOnABeam dialogs may appear distorted, with buttons and fields out of place. As a work-around, you can select "Set custom text size" within the Display control panel & then uncheck "Use Windows XP style scaling". This eliminates the scaling problem within MOAB dialogs at the expense of stretching the UI such that MOAB windows & dialogs may become somewhat blurry. You have to log-off and on again to effect these changes.