[Bugs] #3439 UNSP: Resume state
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Fri Apr 13 11:15:04 EDT 2012
#3439: Resume state
------------------------------------------+---------------------------------
Reporter: humitos | Owner: RafaelOrtiz
Type: defect | Status: new
Priority: Unspecified by Maintainer | Milestone: Unspecified by Release Team
Component: StopWatch | Version: Unspecified
Severity: Unspecified | Keywords:
Distribution: Unspecified | Status_field: Unconfirmed
------------------------------------------+---------------------------------
What's the idea of "Resume state" in StopWatch activity?
I noticed that the behavior is not always the same, and it's quite
strange.
Step to reproduce it:
1. Start a clean StopWatch activity
1. You'll see all the clocks in "0,00"
1. Start some clocks
1. Add some marks to those clocks
1. Stop the activity (remember the times)
1. Resume the activity
* All the mark will be there, and all the clocks will start running
again but they don't resume the last state, instead of this they continued
while you had the activity closed
1. Stop again the activity
1. Resume the activity
* Again, you will see all the marks there, but now the clocks will be
stopped and in 0,00 again.
So, two different behaviors with the same action.
Even more, if you start a new clock this time (the second time that you
resumed the activity) it will be started when you open it again but if you
close and open it again it will be stopped. So, the second time that you
resume the activity the clocks are stopped.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/3439>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list