#3438 HIGH First D: Optimize drawing code and response time of Measure Activity

[Zarro Boogs per Child]

#3438: Optimize drawing code and response time of Measure Activity
-------------------------------+--------------------------------------------
  Reporter:  arjs              |       Owner:  arjs                                    
      Type:  enhancement       |      Status:  new                                     
  Priority:  high              |   Milestone:  First Deployment, V1.0                  
 Component:  measure-activity  |     Version:  Development build as of this date       
Resolution:                    |    Keywords:  optimize drawing, response time, measure
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by arjs):

 * cc: Hello1024 (added)
  * version:  => Development build as of this date


Comment:

 (From #3734)

 Measure peggs the CPU at 100% all the time, wasting a lot of power. This
 is probably due to the slow python drawing code drawing the "line" and the
 background grid continuously.

 Can it be optimised, or is rewrite in C necessary?

 Note that it would be good to have a higher frame rate in measure as well.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3438#comment:10>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system