Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(515)

Unified Diff: ui/events/latency_info.h

Issue 541033003: Added coordinates information to InputLatency (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 6 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: ui/events/latency_info.h
diff --git a/ui/events/latency_info.h b/ui/events/latency_info.h
index 92d928d615837d1323f07112b9244c135af4e67d..029600724927227289c04a1e51c57bae18476fb7 100644
--- a/ui/events/latency_info.h
+++ b/ui/events/latency_info.h
@@ -15,6 +15,8 @@
namespace ui {
+const size_t kMaxLatencyCoordinates = 12;
Sami 2014/09/04 19:10:43 Delete.
cvicentiu 2014/09/05 17:19:57 Done.
+
enum LatencyComponentType {
// ---------------------------BEGIN COMPONENT-------------------------------
// BEGIN COMPONENT is when we show the latency begin in chrome://tracing.
@@ -95,6 +97,8 @@ struct EVENTS_BASE_EXPORT LatencyInfo {
uint32 event_count;
};
+ typedef std::vector<std::pair<int32, int32> > LatencyScreenCoordinates;
Sami 2014/09/04 19:10:43 float InputCoordinates gfx::PointF instead of pa
cvicentiu 2014/09/05 17:19:56 Done.
+
// Empirically determined constant based on a typical scroll sequence.
enum { kTypicalMaxComponentsPerLatencyInfo = 6 };
@@ -153,6 +157,9 @@ struct EVENTS_BASE_EXPORT LatencyInfo {
void TraceEventType(const char* event_type);
LatencyMap latency_components;
+
+ LatencyScreenCoordinates coordinates;
Sami 2014/09/04 19:10:43 InputCoordinates input_coordinates, add a comment
cvicentiu 2014/09/05 17:19:56 Done.
+
// The unique id for matching the ASYNC_BEGIN/END trace event.
int64 trace_id;
// Whether a terminal component has been added.

Powered by Google App Engine
This is Rietveld 408576698