MiceOnABeam Product Documentation

Modified: 2/16/2011 8:23 PM
Recently changed articles You can subscribe to this wiki article using an RSS feed reader.

V1.0.0 Release Notes

What's New

(352) Free and Professional versions of MiceOnABeam are now available:
With the general release of MiceOnABeam there are now two versions of the program to choose from.

The Free version is provided at no cost with the following limitations:

  • LSL code generation is limited to a maximum of five states. Note that script models can still be created or opened which have more than five states. However at code generation time, the state check will be done and the code generation will not proceed if there are more than five states.
  • The Performance Analysis feature is not available.

A Professional version is also available for purchase at Second Life's XStreet Marketplace. This version supports all features and has no limit placed on the number of states in the script model at code generation time.

(365) Peformance Analysis:
MiceOnABeam models can now be automatically instrumented with LSL code to measure and report execution timings for selected components within a script model. This is a powerful new feature that can help you identify performance bottlenecks in your designs.

(379) Multiple property editors can now be opened at the same time:
In previous releases the property editors for States, Transitions, State Variables/Functions and Custom Globals operated in a modal fashion so that no other work could be done in the script model until the editor was closed.

These property editors have now been made non-modal so that multiple editors can be opened at the same time. This makes it much more convenient to consult other areas of the model when working.

Note that editing changes made for States, Transition and Custom Globals property editors are not validated nor saved until the OK button is clicked.

The State Variables/Functions Editor will validate each field as the cursor leaves the field, however changes are not saved until the OK button is clicked.

Also note that deleting the corresponding modeling component for a property editor will result in that property editor being immediately closed with any pending changes discarded. Similarly so for closing a script model with open property editors.

(367) Improved Compiler Directives:
Compiler Directives can now have spaces and tabs prefixing them on a line so that they can be properly indented with the rest of the code. They can now also be included within LSL if statements and looping constructs.

(159) Save button added to Generated Code dialog:
The generated code can now be saved into a text file directly from the Generated Code window.

Clicking on the Save button will bring up a Save As dialog where you can select the directory in which to save the text file. If the file already exists, you will be prompted whether to overwrite the file.

(378) Transitions displayed on top when State Editor opened:
Selecting a modeling component always moves it to the top of the display order so that it's labels are displayed. However this can obscure transition end points.

Now whenever a State Editor is opened, transitions are always displayed on top. Selecting Refresh All in the main program's Window menu will also redraw all open State Editors with their transitions displayed on top.

(386) Default file name for script in Save As dialog now set to script name:
The default file name for a script in the Save As dialog is now set to the script name.

(394) Event argument names now included in code completion:
Event argument names have been added to the Code Completion keywords file for access within the built-in LSL code editor.

(396) Group component moves improved:
Transitions which were only connected on one end to the group of components involved in a group move, had their end points fixed and so did not adjust to the move.

These transitions will now have their end points adjusted during the group move for improved readability.

Note that transitions which are curved will only have their end point connected to the group adjusted.

(387) Default or current name now selected in New Name dialogs or Property Editors:
In previous releases the component name in a New Name dialog or Properties editor had to be first selected in order to be changed when the dialog first opened. Now the text will be automatically selected for convenience.

(400) Transition Notation sub options are now independent from Set Transition Name:
In the Transition panel of the Options dialog, the Include Guard and Include Transition Action items can now be set independently from the Set Transition Name option.

Bug Fixes

(388) Choice Point name was not being updated for trace messages:
If the name of a Choice Point was changed, the new name would not be reflected in transition trace messages. This has been fixed.

(393) Locked entry/exit point didn't move along with state:
This has been fixed.

(403) External Editor issues:
1) When an external editor was opened while editing a modeling component's LSL code segment, any changes made since the last save were deleted and not included in the external editor.

2) Command line arguments specified in the Code Editor panel of the Options dialog were not being handled properly and could result in the external editor failing to open.

Both of these issues have been fixed.

(399) With auto-naming disabled New Name dialog did not show next available name:
When Auto name design elements is disabled in the Models panel of the Options dialog, you are prompted for a name each time a new modeling component is created.

In previous releases the New Name Dialog was initialized to the standard default name for each component. Now the dialog will be initialized to the next available name for the component.

(392) Selected transition points left selection rectangle on State Editor resize:
The selection rectangle for entry/exit points on the border of a State Editor will now be cleared upon resizing or moving the State Editor.

Known Issues

(132) Moving a State Editor window will clear the Undo/Redo history.

(405) Can't close a State Variables/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 Close Box or ESC key. In this case the Cancel button should be used to abort the changes.

Tags:
Home: MiceOnABeam Product Documentation Copyright © 2010-2018 MiceOnABeam Software