ui::LatencyInfo includes both event and frame production timing info: Maybe we can split that up? |
|||
Issue descriptiongpu/ipc/common depends on ui/events for ui::LatencyInfo. This is a little bit odd because gpu code shouldn't have anything to do with events. It might be nice to split ui::LatencyInfo in two pieces: FrameLatencyInfo and EventLatencyInfo or whatever names make the most sense.
,
Mar 24 2016
Thanks for filing a bug. FrameLatencyInfo and EventLatencyInfo SGTM. There's some longer term work to be done here as well, but I think splitting this up is a good first step. We might still end up with a LatencyInfo object that holds a FrameLatencyInfo and an EventLatencyInfo, to simplify some of the plumbing.
,
Apr 12 2016
I'm marking this as won't fix. We decided it would be easier (for now) to move LatencyInfo to ui/latency_info and depend on that instead. https://codereview.chromium.org/1871233002/ |
|||
►
Sign in to add a comment |
|||
Comment 1 by piman@chromium.org
, Mar 24 2016