State transactions in simulations makes it difficult to edit variable values

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create 2 Regions. In one region make two states each getting triggered after 
100ms from other state

[state 1]---after 100ms--->[state 2]
[_______]<--after 100ms--->[_______]

2. In region 2 create a variable based transition.

[state 2]---[variable > 1000]--->[state 2]

3. Start simulation.

What is the expected output? What do you see instead?
At normal human speed while simulation is running no one will be able to change 
value of variable to 1000. At max one can write 100 at while simulation is 
cycle based 200ms.

What version of the product are you using? On what operating system?
SCT 2 with Eclipse Juno. Windows 7 SP1.

Original issue reported on code.google.com by skbob...@gmail.com on 17 Oct 2012 at 2:48

[GoogleCodeExporter]

Thank you for the bug report. It is a known issue that is scheduled to be fixed 
during november. 

Original comment by AxelTerfloth on 17 Oct 2012 at 10:40

[GoogleCodeExporter]

Simulation Interface will be reimplemented. So far you have to pause the 
simulation for value changes.

Original comment by AxelTerfloth on 20 Dec 2012 at 8:05

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by AxelTerfloth on 20 Dec 2012 at 8:06

• Added labels: SCT-2.0
• Removed labels: Milestone-Release1.2.x

[GoogleCodeExporter]

Original comment by AxelTerfloth on 20 Dec 2012 at 8:11

• Added labels: Milestone-SCT-2.0
• Removed labels: SCT-2.0

[GoogleCodeExporter]

Original comment by A.Muel...@googlemail.com on 29 Sep 2014 at 12:36

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by AxelTerfloth on 29 Sep 2014 at 2:05

• Added labels: archived