Last updated field keeps running after pressing stop

J2R5M3 / evolutionchamber

Automatically exported from code.google.com/p/evolutionchamber

0 stars 0 forks source link

Last updated field keeps running after pressing stop #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Run the app
2. Select target state
3. Press Start
4. Press Stop

What is the expected output? What do you see instead?
I expect all the counters to be stopped displaying the last value or a default 
text.
The last update counter keeps running.

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.
Also the field on the left is shorter hence the separator and Last Update label 
slightly hovers over the first field.

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

GoogleCodeExporter commented 8 years ago

Setting the variable lastUpdate to 0 in the actionlistener for the stop button 
eliminates this problem I think :)

Original comment by cellstr...@gmail.com on 18 Oct 2010 at 7:53

GoogleCodeExporter commented 8 years ago

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

Added labels: Component-UI, Usability

GoogleCodeExporter commented 8 years ago

Is this bad? It is still telling you when the last update to the build was, 
just from the current time rather than the time when the chamber stopped 
running.

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

GoogleCodeExporter commented 8 years ago

I believe it is bad. That information brings no value if the application is not 
running. I think it's initial purpose was to hint the user that the 
calculations are still taking place and to help him notice that the BO changed 
recently. If we know that the BO will no longer change (because the application 
is stopped) then I see no reason to keep the counter running. Am I correct?

Original comment by netpr...@gmail.com on 19 Oct 2010 at 8:10

GoogleCodeExporter commented 8 years ago

Fixed.

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

Changed state: Fixed
Added labels: Milestone-0005

GoogleCodeExporter commented 8 years ago

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

Changed state: Verified