History log of /frameworks/base/tools/layoutlib/bridge/src/android/view/RenderNode_Delegate.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
2a1b23966af3a9ee25cd223e1679f08beb8ed072 02-Feb-2017 Diego Perez <diegoperez@google.com> Update native delegates

After changes 9ff994d98846, 6e3658a63843 and 18e9f9f37783
Test: Existing layoutlib tests

Change-Id: I8e39f26ccb0a8cb73a724f16734e66cf95c08656
/frameworks/base/tools/layoutlib/bridge/src/android/view/RenderNode_Delegate.java
f666c0e2eaceb265069a77c520e84c1a08f08ae4 24-Nov-2016 Jerome Gaillard <jgaillard@google.com> Fix layoutlib to reflect recent changes in platform code

Test: Layoutlib tests
Change-Id: I81964233a9e580ccee9c9e9b0cf3525babf30bd4
/frameworks/base/tools/layoutlib/bridge/src/android/view/RenderNode_Delegate.java
8f43dfef2bf4581fa97705ffaabf66b7568b9544 04-Apr-2016 Diego Perez <diegoperez@google.com> Update Path and RenderNode delegates to new API

RenderNode_Delegate nCreate now takes a reference to this. In the
Path_Delegate, the native_offset call with a destination path has been
removed.

Change-Id: I6332bb4733974b817e8a29eab82e2218fcf942c4
/frameworks/base/tools/layoutlib/bridge/src/android/view/RenderNode_Delegate.java
ded4d14e3348ebb0cdfa3498a53d3fbfc58b2043 21-Jan-2016 Jerome Gaillard <jgaillard@google.com> Deals with translation and scaling in layoutlib

Layoutlib now correctly interprets the translation and scaling
xml attributes of views, by implementing what the Android platform
does in native code.

Change-Id: Ie8465f40ef4508d3c31796200800f12cb8f883a4
/frameworks/base/tools/layoutlib/bridge/src/android/view/RenderNode_Delegate.java
c92d70dff716a8b38982b3d6ec05427ad66497fa 19-Jan-2016 Jerome Gaillard <jgaillard@google.com> Deals with android:rotation attribute in layoutlib

The way Android views deal with their rotation xml attribute is through
native code called for hardware accelerated rendering. So layoutlib
has to bypass that in order to take those attributes into account.

Bug: http://b.android.com/73300
Change-Id: Ieb5bf0567a25a9021491ebf3250cedd0752f7863
/frameworks/base/tools/layoutlib/bridge/src/android/view/RenderNode_Delegate.java
796e9b7f9910f2ba8133cdb6f137107585b2e5fa 05-Nov-2014 Deepanshu Gupta <deepanshu@google.com> Add primitive shadows support to LayoutLib

The shadows rendered are not the same as rendered by the framework. The
main purpose of the shadows here is let the user know when shadows will
be cast.

Currently rectangular shadows are available in only two intensities. Any
elevation below 10dp uses one shadow and any elevation over 10 dp uses
the other.

Also, even though the code for arbitrary shapes exist, it doesn't quite
work yet. No shadows are visible when that code is run.

Change-Id: Ie8235ffccf1d3809713f5d8f82afde434817d6b2
/frameworks/base/tools/layoutlib/bridge/src/android/view/RenderNode_Delegate.java