#7894 NORM 9.1.0: Colors activity shouldn't turn on the camera except when it's using it

[Zarro Boogs per Child]

#7894: Colors activity shouldn't turn on the camera except when it's using it
-----------------------------+----------------------------------------------
   Reporter:  gnu            |       Owner:  wadeb        
       Type:  defect         |      Status:  new          
   Priority:  normal         |   Milestone:  9.1.0        
  Component:  new component  |     Version:  not specified
 Resolution:                 |    Keywords:               
Next_action:  diagnose       |    Verified:  0            
  Blockedby:                 |    Blocking:               
-----------------------------+----------------------------------------------

Comment(by wadeb):

 Colors uses the camera for two features:

 1) It supports taking snapshots which can be displayed as a "background"
 to paint over, for example if you wanted to "trace" a real life scene in
 the program.

 2) It supports a "video paint" mode where a green object can be held in
 front of the camera and moved around like a cursor.  At the time it was
 implemented, I felt that given the non-working nature of the PT and the
 inaccuracy of the GS, this was the best painting method.

 Originally I tried toggling the camera as needed, but GStreamer was
 crashing IIRC.   I think the ideal fix will be to integrate Nirav Patel's
 PyGame vision processing library but I'm not sure when that will be
 available.

 I will look at it again as soon as I get a working development environment
 set up.

 Colors has other power related issues as well.  It needs to detect when
 there is no activity and go to sleep.  Currently it continually renders
 even when painting and scrolling are not active.

-- 
Ticket URL: <http://dev.laptop.org/ticket/7894#comment:3>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system