#7700 NORM Future : Inconsistent effective ticking rates for some morphs

[Zarro Boogs per Child]

#7700: Inconsistent effective ticking rates for some morphs
----------------------------+-----------------------------------------------
 Reporter:  ScottWallace    |         Owner:  etoys                            
     Type:  defect          |        Status:  new                              
 Priority:  normal          |     Milestone:  Future Release                   
Component:  etoys-activity  |       Version:  Development build as of this date
 Keywords:                  |   Next_action:  design                           
 Verified:  0               |     Blockedby:                                   
 Blocking:                  |  
----------------------------+-----------------------------------------------
 Morph subclasses which reimplement #stepTime often do not attain the
 desired ticking-rate in a ticking etoy script, because the stepTime
 governs how often the morph's "player" gets steps, which in turn can
 affect the effective ticking rate.  Etoys3.0 update 1064polyStep-sw fixed
 one such situation -- the most egregious one, regarding polygonMorphs,
 which are frequently scripted by etoy users.  But the ninety some-odd
 other reimplementors of #stepTime need to be scrutinized and most (or all)
 that specify stepTimes larger than 10 (the standard value for morphs with
 players) probably need to be adjusted to assure that they get stepped at
 least once every 10 ms when there is a player associated with them.

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