[Sugar-devel] stopwatch activity

Sameer Verma sverma at sfsu.edu
Wed Apr 28 01:14:29 EDT 2010


On Tue, Apr 27, 2010 at 8:00 PM, Benjamin M. Schwartz
<bmschwar at fas.harvard.edu> wrote:
> On Tue, 27 Apr 2010, Sameer Verma wrote:
>
>> I noticed something interesting with he stopwatch activity on the XO
>> 1.5 C2 with build 120. When the XO goes into suspend, the clock stops
>> display, but upon resume, will show actual time elapsed (clock keep
>> counting).  "Mark" also works correctly, displaying the time when the
>> "Mark" button is clicked, irrespective of the display.  I'm not sure
>> what the behavior should be, though.
>
> I think that's fine behavior.  Most stopwatches don't stop running by
> themselves, so I don't see why ours should.
>

Indeed, so when the numbers stop at a certain point, it looks strange.

>> Should the activity prevent suspend?
>
> My philosophy is that suspend should be _absolutely transparent_ to the
> user; i.e. its effects should not be detectable, in the same way that
> processor voltage scaling is undetectable.
>
> This suggests that Stopwatch should inhibit suspend while it is visible
> onscreen.  I'm reluctant to do this, though, because it feels like an ugly
> hack.  The right solution would be for the suspend system to recognize that
> Stopwatch has a timer set to expire in 100 ms, and postpone suspend.
>
> --Ben
>
>

Sameer

-- 
Dr. Sameer Verma, Ph.D.
Associate Professor, Information Systems
Director, Campus Business Solutions
San Francisco State University
http://verma.sfsu.edu/
http://opensource.sfsu.edu/
http://cbs.sfsu.edu/
http://is.sfsu.edu/


More information about the Sugar-devel mailing list