Issue 1729343004: Reverse scene node drawing order.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 1729343004: Reverse scene node drawing order. (Closed)

Created:
4 years, 10 months ago by jeffbrown

Modified:
4 years, 10 months ago

Reviewers:
abarth

CC:
Aaron Boodman, abarth-chromium, ben+mojo_chromium.org, darin (slow to review), gregsimon, mojo-reviews_chromium.org, qsr+mojo_chromium.org, viettrungluu+watch_chromium.org

Base URL:
git@github.com:domokit/mojo.git@master

Target Ref:
refs/heads/master

Project:
mojo

Visibility:
Public.

More Reviews

Description

Reverse scene node drawing order. It makes more sense to draw parents before children such as when drawing a background. BUG= R=abarth@google.com Committed: https://chromium.googlesource.com/external/mojo/+/8e372239f71dce2a2bd29278d4016371cb4b5575

Patch Set 1 #

Created: 4 years, 10 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+9 lines, -13 lines)			Patch
	M	mojo/services/gfx/composition/interfaces/nodes.mojom	View		1 chunk	+3 lines, -3 lines	0 comments	Download
	M	services/gfx/compositor/graph/node_def.cc	View		3 chunks	+6 lines, -10 lines	0 comments	Download

Messages

Total messages: 5 (2 generated)

Expand Messages | Collapse Messages | Show Generated Messages | Hide Generated Messages

jeffbrown

4 years, 10 months ago (2016-02-24 22:12:00 UTC) #5

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
8e372239f71dce2a2bd29278d4016371cb4b5575 (presubmit successful).

Expand Messages | Collapse Messages | Show Generated Messages | Hide Generated Messages