blob: 8ebd5d2f7231d72a52dc70ac4f8262e87effae11 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" >
<title>eTrice Documentation</title>
<link rel="stylesheet" type="text/css" href="css/book.css"/>
<link rel="stylesheet" type="text/css" href="css/custom-common.css"/>
</head>
<body>
<h1><a href="#release-notes" name="release-notes"></a>Release Notes</h1>
<p>Noteworthy release changes are described here.</p>
<h2><a href="#2-0-0-migration" name="2-0-0-migration"></a>2.0.0 Migration</h2>
<p><span class="label label-danger">Breaking Changes:</span> This release contains a breaking change to models used with previous versions.</p>
<p>The name of the data for protocol messages is not longer used and is marked as deprecated. In state machines the message data is now named <code>transitionData</code>. Thus <strong>all occurrences of the message data have to be renamed</strong>. The changes to the model are depicted in the picture below:</p>
<p><img src="images/600-TransitionDataMigration.png" alt="image"></p>
<p>eTrice provides a <strong>migration action</strong> which automatically applies the modification to a complete model file. But it is not guaranteed to find all instances of the message data, thus it may be necessary to apply the changes manually. The migration can be triggered via editor right click and hitting <em>Migration Transition Data Style</em> action.</p>
<p><img src="images/600-TransitionDataMigrationAssitant.png" alt="image"></p>
<p><span class="label label-info">Note:</span> The migration assistant relies on the message data names, thus the names should not be removed until you have fully migrated your project and all dependent projects.</p>
<br>
<p>In addition eTrice now uses the so-called <em>Smart Strings</em> for user code. This is not a breaking change, but it is recommended to migrate to this new syntax also. Using the Transition Data migration action will automatically convert all affected user codes into Smart Strings. Further there is a dedicated migration action for the Smart Strings, see <strong>Migrate to Smart Action Codes</strong> above. Additionally there is a quickfix available:</p>
<p><img src="images/600-DetailcodeMigration.png" alt="image"></p>
</body>
</html>
|
