This example needs and processes: Activity loads the custom surfaceview-> Surfaceview constructor: Initializes the brush, sensor, Surfaceholder and register Surfaceholder Monitor (surfacecreated and surfacedestroyed), create surface that is surfacecreated: Register sensor monitoring, Initialize the ball (including the picture, position, active area), start the Thread and loop execution (according to the acceleration of shaking to determine whether the ball future coordinates are out of bounds, the range is changing the speed direction is rebound, not out of bounds then set the future coordinates, the ball is drawn to the new coordinates)
This example revelation: 1. Surfaceview is used for dynamic rendering of view; 2. Surfaceview often needs to loop through a thread to update the view in real time; 3. Why must I use Surfaceview? View line? No, only with Surfaceview can we further use Surfaceholder and how to manage surface life cycle and how to draw it;
Sample Demo demo (Shake a Ball bump)
Custom Controls (2.3): Surfaceview and Surfaceholder
