Jason Simmons ced3e0d1e5 Initialize the engine in the running state to match the animator's default state (flutter/engine#11011) ...

The engine's activity_running flag tracks whether the app is in the paused or
running lifecycle state.  The engine had been defaulting activity_running to
false (meaning paused).  But the animator had been defaulting its paused flag
to false, which allowed frames to render at startup.  If the engine loses and
regains its surface, then frames would stop rendering because activity_running
is false (even though frames had been rendering when the engine initially
acquired its surface).

This change puts the engine and the animator into a consistent state at
startup.  Frames will continue to render until the embedder sends a lifecycle
message that will pause both the engine and the animator.

See https://github.com/flutter/flutter/issues/32624

2019-08-14 16:20:44 -07:00

..

src/flutter

Initialize the engine in the running state to match the animator's default state (flutter/engine#11011)

2019-08-14 16:20:44 -07:00