5cd467f3a0
The previous approach re-inflated views on every frame simply because the FPS number changed (which was passed in a JSON object and used to check whether the old view matched the new one based on a tag on the view that was set by the previous FPS string). The new approach is not pretty (there's no reason to even re-populate the views when the only thing that needs to happen is to set the appropriate FPS info in the floating TextView), but at least this avoids the inflation overhead of the previous approach. BUG=skia: Change-Id: Ide1c736c49663cfcf478653a7cdaa99c736f1783 Reviewed-on: https://skia-review.googlesource.com/8461 Reviewed-by: Derek Sollenberger <djsollen@google.com> Commit-Queue: Chet Haase <chet@google.com> |
||
---|---|---|
.. | ||
android | ||
ios/bin |