https://sourceforge.net/p/ucgn/feature-requests/2011-02-17T17:03:24ZRecent changes to feature-requests2011-02-17T17:03:24Z2011-02-17T17:03:24ZKai Harthhttps://sourceforge.net/u/kharth/https://sourceforge.net98b615e7fe8b37b33a202269f748024daee17361

<div class="markdown_content"><p>Mathworks has apparently relaxed their transition evaluation semantics in an undocumented way.</p> <p>Example: A state "A" has two outgoing transitions, both of which are bare (no guard condition). The guard condition occurs downstream on another transition, after going through a junction.</p> <p>While this makes sense it was originally not allowed under a stricter evaluation of the published semantics... Transition "2" would be shadowed by transition "1".</p> <p>Oddly enough, if such a chart is compiled in Simulink with the chart set to use implicit transition ordering (without actually resulting in a different order), a coder warning is generated by simulink...<br /> "Chart #1056 has an unconditional transition #1062 that shadows<br /> the following transitions: #1063 #1064"<br /> but the generated RTW code is correct despite that warning. </p></div>

2011-02-17T16:57:35Z2011-02-17T16:57:35ZKai Harthhttps://sourceforge.net/u/kharth/https://sourceforge.netbb4f533515745827fd06171fe9935c8bfd346e64

<div class="markdown_content"><p>The current UCGN/Simulink can not handle flowgraph loops in Stateflow, but this would be a strong feature to have.</p></div>

2011-02-01T19:32:19Z2011-02-01T19:32:19ZKai Harthhttps://sourceforge.net/u/kharth/https://sourceforge.net8c6186dc65c754c7eb5c2ddee26ab5ee78821273

<div class="markdown_content"><p>The newer releases of Simulink support the use of true enumerated type definitions. These should be available for UCGN/Simulink as well...</p></div>

2010-11-02T11:43:48Z2010-11-02T11:43:48ZKai Harthhttps://sourceforge.net/u/kharth/https://sourceforge.netdf7123d066f68a0e339590ac9c9f6d33175d9f95

<div class="markdown_content"><p>Currently for Stateflow only the implicit (automatic) ordering of transitions si supported.<br /> Consider adding support for using the user explicit ordering of transitions.<br /> (originally this limitation was intentionally, because user explicit ordering of transition evaluation reduced the readability of charts... but Stateflow has improved the visibility of those ordering choices) </p></div>

2010-07-19T12:40:04Z2010-07-19T12:40:04ZKai Harthhttps://sourceforge.net/u/kharth/https://sourceforge.net063ab507ab5f5a2efdaaece8af7c5280d5255444

<div class="markdown_content"><p>Provide forward inlining capability for BusCreator members.</p> <p>Forward inlining is when a downstream entity is used upstream, instead of creating an intermediate variable:</p> <p>Currently:</p> <p>GBL_Types_Double OutputValue;</p> <p>MySubsystemCall(Input1, Input2, &amp;OutputValue);</p> <p>BusCreator.Value = Outputvalue;</p> <p>Desired:</p> <p>MySubsystemCall(Input1, Input2, &amp;(BusCreator.Value));</p></div>

2010-06-24T00:45:44Z2010-06-24T00:45:44ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net295e1ba0fb6785e1ac4597db12dab9aa35aff7d4

<div class="markdown_content"><p>Add History connector capabilities to Stateflow model transformation </p></div>

2010-06-23T15:06:16Z2010-06-23T15:06:16ZKai Harthhttps://sourceforge.net/u/kharth/https://sourceforge.net57be3765b5e0b225b2f711dd54ac3e5ed352c50e

<div class="markdown_content"><p>Add capability to process and generate output for For and While Iterator Subsystems</p></div>

2010-06-23T15:05:12Z2010-06-23T15:05:12ZKai Harthhttps://sourceforge.net/u/kharth/https://sourceforge.net494c25c4b74abe09b668db815f2f16cdeeca1fab

<div class="markdown_content"><p>Add the capability to process and generate output for Enabled Triggered Subsystems</p></div>