diff options
| author | dominikg@chromium.org <dominikg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-23 17:04:50 +0000 |
|---|---|---|
| committer | dominikg@chromium.org <dominikg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-23 17:04:50 +0000 |
| commit | daea3d424f865ae7fc5720dea7b3c9565952a968 (patch) | |
| tree | 0c6bf0ade3676ee7b735fbc0aa5e1872cef9475f /cc/scheduler | |
| parent | f54f8ce7166114c58c6ecb92b6cc2a0f8bac0a2b (diff) | |
| download | chromium_src-daea3d424f865ae7fc5720dea7b3c9565952a968.zip chromium_src-daea3d424f865ae7fc5720dea7b3c9565952a968.tar.gz chromium_src-daea3d424f865ae7fc5720dea7b3c9565952a968.tar.bz2 | |
Rename BeginFrame to BeginMainFrame and BeginImplFrame (part 3).
Third patch in a series to rename BeginFrame. This patch focuses on
cc::ThreadProxy, cc::LayerTreeHost, cc::LayerTreeHostImpl, cc::OutputSurface
and it's related (sub)classes.
In the scheduler, the term 'BeginFrame' is used for both the main thread and the
impl thread. This can cause confusion if it's not obvious which one is being
refered to. To clarify this, we rename BeginFrame to BeginMainFrame and
BeginImplFrame, respectively.
BUG=261765
Review URL: https://codereview.chromium.org/35023002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230453 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/scheduler')
| -rw-r--r-- | cc/scheduler/scheduler_state_machine.cc | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/cc/scheduler/scheduler_state_machine.cc b/cc/scheduler/scheduler_state_machine.cc index 227d5ed..0e86382 100644 --- a/cc/scheduler/scheduler_state_machine.cc +++ b/cc/scheduler/scheduler_state_machine.cc @@ -823,7 +823,7 @@ bool SchedulerStateMachine::BeginImplFrameNeededToDraw() const { // These are cases where we are very likely to draw soon, but might not // actually have a new frame to draw when we receive the next BeginImplFrame. // Proactively requesting the BeginImplFrame helps hide the round trip latency -// of the SetNeedsBeginFrame request that has to go to the Browser. +// of the SetNeedsBeginImplFrame request that has to go to the Browser. bool SchedulerStateMachine::ProactiveBeginImplFrameWanted() const { // The output surface is the provider of BeginImplFrames, // so we are not going to get them even if we ask for them. @@ -850,9 +850,10 @@ bool SchedulerStateMachine::ProactiveBeginImplFrameWanted() const { return true; // If we just swapped, it's likely that we are going to produce another - // frame soon. This helps avoid negative glitches in our SetNeedsBeginFrame - // requests, which may propagate to the BeginImplFrame provider and get - // sampled at an inopportune time, delaying the next BeginImplFrame. + // frame soon. This helps avoid negative glitches in our + // SetNeedsBeginImplFrame requests, which may propagate to the BeginImplFrame + // provider and get sampled at an inopportune time, delaying the next + // BeginImplFrame. if (last_frame_number_swap_performed_ == current_frame_number_) return true; |