June 25, 2009

Dear Reactis User:

We are pleased to announce the availability of Reactis V2009.0.4, V2008.0.13, and Reactis V2009.1.2 (beta).

V2009.1.2 (beta)

New Signal Tracing Feature

Clicking on a signal line in Reactis now highlights the signal in yellow. This feature makes it easy to trace a signal back to the point where it was generated and forwards to the point where it is consumed (used by a block to compute a new value). The highlighting flows through (backwards and forwards) the following blocks that do not modify a signal value: Inport, Outport, Subsystem, From, Goto, DataStoreWrite, DataStoreRead. Highlighting can be removed by clicking in open space.

Other Improvements

• The contents of the log window in the "runtests" utility can now be saved to a file.
• When hovering over a macro in C, the expanded macro text is displayed.
• When trying to set a breakpoint in C code on a line that does not contain an executable statement, Reactis remaps the breakpoint to a different line according to the following rules:
  • If the attempted breakpoint line is within a multiline executable statement, the breakpoint is placed at the first line of multiline statement.
  • It the attempted breakpoint line is on a line with no executable statement (e.g. a comment or a variable declaration) then the breakpoint is placed on the first subsequent line that contains an executable statement.

Bugs fixed since V2009.1.1

• Display proper error message when encountering a static struct variable with undefined size in C.
• Fixed crash when closing the "Coverage Details" window invoked from the Tester results screen.
• Fixed bug where spurious red dots (MC/DC coverage markers) would sometimes be displayed on the top left of the screen in the "Coverage Details" window invoked from the Tester results screen.
• Fixed bug that caused some signal labels to be drawn in the wrong place.
• Display configuration variables in the "Configuration variables" tree item instead "C libraries" tree item. This could happen for models that use both custom C code and configuration variables.
• Properly create cache (.rso) files for Stateflow custom C source code.
• Fixed crash that could occur when undoing a port type change after performing a "synchronize" operation in the RSI file editor.
• Fixed "lost connection to backend" error that would occur if the MATLAB version is set to "use Windows path".
• Fixed bug where Tester and Simulator (would in rare cases) report more than 100% condition coverage.
• Fixed problems during CSV import if the imported value is empty (i.e. two consecutive commas). Reactis now interprets such values as zero.
• Fixed bug that caused wrong line number to be displayed when reporting errors during CSV import.

V2009.0.4

The following bugs were fixed since V2009.0.3:

• Fixed crash that could occur when undoing a port type change after performing a "synchronize" operation in the RSI file editor.
• Fixed "lost connection to backend" error that would occur if the MATLAB version is set to "use Windows path".
• Fixed bug where Tester and Simulator would (in rare cases) report more than 100% condition coverage.
• Fixed problems during CSV import if the imported value is empty (i.e. two consecutive commas). Reactis now interprets such values as zero.
• Fixed bug that caused wrong line number to be displayed when reporting errors during CSV import.

V2008.0.13

The following bugs were fixed since V2008.0.12:

• Fixed crash that could occur when undoing a port type change after performing a "synchronize" operation in the RSI file editor.
• Fixed "lost connection to backend" error that would occur if the MATLAB version is set to "use Windows path".
• Fixed bug where Tester and Simulator would (in rare cases report) more than 100% condition coverage.
• Fixed problems during CSV import if the imported value is empty (i.e. two consecutive commas). Reactis now interprets such values as zero.
• Fixed bug that caused wrong line number to be displayed when reporting errors during CSV import.

You may download the patches or full installers from the Reactis User Pages.

Best Regards,
The Reactis Team