Chromium Code Reviews| Index: ui/events/latency_info.h |
| diff --git a/ui/events/latency_info.h b/ui/events/latency_info.h |
| index 92d928d615837d1323f07112b9244c135af4e67d..ff980404c218915f1192b509613d0ec10caa4c73 100644 |
| --- a/ui/events/latency_info.h |
| +++ b/ui/events/latency_info.h |
| @@ -12,6 +12,7 @@ |
| #include "base/containers/small_map.h" |
| #include "base/time/time.h" |
| #include "ui/events/events_base_export.h" |
| +#include "ui/gfx/point_f.h" |
| namespace ui { |
| @@ -95,6 +96,8 @@ struct EVENTS_BASE_EXPORT LatencyInfo { |
| uint32 event_count; |
| }; |
| + typedef std::vector<gfx::PointF> InputCoordinates; |
|
Yufeng Shen (Slow to review)
2014/09/08 18:29:01
I know Jared has concern about dynamic memory allo
jdduke (slow)
2014/09/08 20:12:20
Yeah, a vector is a definite no-no here, and an ar
|
| + |
| // Empirically determined constant based on a typical scroll sequence. |
| enum { kTypicalMaxComponentsPerLatencyInfo = 6 }; |
| @@ -153,6 +156,10 @@ struct EVENTS_BASE_EXPORT LatencyInfo { |
| void TraceEventType(const char* event_type); |
| LatencyMap latency_components; |
| + |
| + // These coordinates represent window coordinates. |
| + InputCoordinates coordinates; |
| + |
| // The unique id for matching the ASYNC_BEGIN/END trace event. |
| int64 trace_id; |
| // Whether a terminal component has been added. |