Fields in editable state after starting the calculation

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open the app
2. Enter the desired target state
3. Press start

What is the expected output? What do you see instead?
If a field is left enabled, I expect that any changes made to that field are 
reflected in the running process. If changing the value of a field after 
pressing Start doesn't affect the application that field should be grayed out 
until I press Stop.

What version of the product are you using? On what operating system?

version 0002 on MS Windows Vista Home Premium SP2

java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)

Please provide any additional information below.
Leaving the fields enabled can lead to confusion when a user changes the target 
state after running the application making him believe that the app will go 
towards the new goal. This would lead to dedicating computing time on an 
unintended goal.
The second problem I see here is the number of processors setup. It can be 
important for some users to change if they need processor power - finding out 
that the setting has no effect after starting the app is unpleasant.

Original issue reported on code.google.com by netpr...@gmail.com on 18 Oct 2010 at 6:51

[GoogleCodeExporter]

Original comment by netpr...@gmail.com on 18 Oct 2010 at 8:12

• Added labels: Component-UI, Usability

[GoogleCodeExporter]

Original comment by Frit...@gmail.com on 18 Oct 2010 at 8:58

• Changed state: Accepted

[GoogleCodeExporter]

Fixed.

Original comment by Frit...@gmail.com on 19 Oct 2010 at 11:42

• Changed state: Fixed
• Added labels: Milestone-0005

[GoogleCodeExporter]

Original comment by netpr...@gmail.com on 22 Oct 2010 at 5:49

• Changed state: Verified