RSARTE 10 2016.29

The deliveries from sprint 2016.29 are now available. This sprint we will only ship an update of our RSARTE 10 stream. The 9.1.2 CP1 stream is in maintenance mode and during this sprint we did not receive any critical items that had to be fixed. Instead we have included an update (version 5.1) of our Model Fixup utility. The main improvement in this area is support for RSARTE 10 and Eclipse Mars. See the Model Fixup page for more information.

In the RSARTE 10 drop we have included a number of usability enhancements as well as a number of fixes in the (still experimental) new search feature.

The usability improvements include:

• A compare/merge user interface improvement where the code editor area is increased to show more of the code snippets.
• Some fixes in the project explorer where now more useful keywords are shown for elements in activity diagrams.
• An improvement in the property pages where the sort order for the signature column now is preserved when you switch between model elements.
• A change in the behaviour when modifying the type of e.g. an attribute. We now no longer loose the default value when the type is changed.
• Navigation from a state symbol to sub state machine diagrams has been improved for the fairly common case where there is inheritance between state machines.

You can find more details about the fixes in the WhatsNew presentation. See pages 16, 20, 21, 22 and 23.

In the search area we have also in this sprint focused on the key search work flow: Searching, investigating the search results and navigating to found matches. The improvements in this area includes:

• The text for matching references has been improved, now showing more information. For example we now show the name of an attribute that has a type that matches the search query.
• The navigation menu has been extended, allowing more direct navigation to various elements related to the search match.
• It is now possible to copy the search result and paste e.g. in a spreadsheet.
• Highlighting of search results in the Code editor is now supported.
• We now have support for finding matches in native type references.
• The association between matches in code snippets and model elements has been improved. Previously the matches were associated only with opaque elements, now they are associated with the container, for example an operation.