Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 // Copyright 2016 The Chromium Authors. All rights reserved. | 1 // Copyright 2016 The Chromium Authors. All rights reserved. |
| 2 // Use of this source code is governed by a BSD-style license that can be | 2 // Use of this source code is governed by a BSD-style license that can be |
| 3 // found in the LICENSE file. | 3 // found in the LICENSE file. |
| 4 | 4 |
| 5 module ui.mojom; | 5 module ui.mojom; |
| 6 | 6 |
| 7 import "mojo/common/time.mojom"; | 7 import "mojo/common/time.mojom"; |
| 8 import "ui/gfx/geometry/mojo/geometry.mojom"; | 8 import "ui/gfx/geometry/mojo/geometry.mojom"; |
| 9 | 9 |
| 10 enum LatencyComponentType { | 10 enum LatencyComponentType { |
| (...skipping 57 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 68 // This component indicates that the input causes a commit to be scheduled | 68 // This component indicates that the input causes a commit to be scheduled |
| 69 // but the commit was aborted since it carried no new information. | 69 // but the commit was aborted since it carried no new information. |
| 70 INPUT_EVENT_LATENCY_TERMINATED_COMMIT_NO_UPDATE_COMPONENT, | 70 INPUT_EVENT_LATENCY_TERMINATED_COMMIT_NO_UPDATE_COMPONENT, |
| 71 // This component indicates that the input causes a swap to be scheduled | 71 // This component indicates that the input causes a swap to be scheduled |
| 72 // but the swap failed. | 72 // but the swap failed. |
| 73 INPUT_EVENT_LATENCY_TERMINATED_SWAP_FAILED_COMPONENT, | 73 INPUT_EVENT_LATENCY_TERMINATED_SWAP_FAILED_COMPONENT, |
| 74 LATENCY_COMPONENT_TYPE_LAST = | 74 LATENCY_COMPONENT_TYPE_LAST = |
| 75 INPUT_EVENT_LATENCY_TERMINATED_SWAP_FAILED_COMPONENT, | 75 INPUT_EVENT_LATENCY_TERMINATED_SWAP_FAILED_COMPONENT, |
| 76 }; | 76 }; |
| 77 | 77 |
| 78 enum SourceEventType { | |
| 79 UNKNOWN, | |
| 80 WHEEL, | |
| 81 TOUCH, | |
| 82 OTHER, | |
| 83 SOURCE_EVENT_TYPE_LAST = OTHER, | |
|
tdresser
2017/04/27 14:39:27
Is there some assertion we can add to reduce the r
mfomitchev
2017/04/27 22:06:28
What if we add an assert for ui::mojom::LATENCY_CO
Fady Samuel
2017/04/27 22:49:25
We deal with this problem in cc via SetAll/SetNew
| |
| 84 }; | |
| 85 | |
| 78 struct LatencyComponentId { | 86 struct LatencyComponentId { |
| 79 LatencyComponentType type; | 87 LatencyComponentType type; |
| 80 int64 id; | 88 int64 id; |
| 81 }; | 89 }; |
| 82 | 90 |
| 83 struct LatencyComponent { | 91 struct LatencyComponent { |
| 84 // Nondecreasing number that can be used to determine what events happened | 92 // Nondecreasing number that can be used to determine what events happened |
| 85 // in the component at the time this struct was sent on to the next | 93 // in the component at the time this struct was sent on to the next |
| 86 // component. | 94 // component. |
| 87 int64 sequence_number; | 95 int64 sequence_number; |
| (...skipping 12 matching lines...) Expand all Loading... | |
| 100 LatencyComponent value; | 108 LatencyComponent value; |
| 101 }; | 109 }; |
| 102 | 110 |
| 103 // See ui/latency/latency_info.h | 111 // See ui/latency/latency_info.h |
| 104 struct LatencyInfo { | 112 struct LatencyInfo { |
| 105 string trace_name; | 113 string trace_name; |
| 106 array<LatencyComponentPair> latency_components; | 114 array<LatencyComponentPair> latency_components; |
| 107 int64 trace_id; | 115 int64 trace_id; |
| 108 bool coalesced; | 116 bool coalesced; |
| 109 bool terminated; | 117 bool terminated; |
| 118 SourceEventType source_event_type; | |
| 110 }; | 119 }; |
| OLD | NEW |