Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library.
Bug: 145132366
Test: m && diff unsupportedappusage_index.csv
Change-Id: I8ffa1da1bcd43c25f4ff817575db77a33c0f3d31
The old API was a shim over the new API, and will be deleted soon.
The new API is actually public, simpler, and more powerful.
Test: Everything still builds.
Change-Id: I11af8da9132e23a070e87dd5a7401c4854dd102a
Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library.
Bug: 145132366
Test: m && diff unsupportedappusage_index.csv
Change-Id: I4bc8c9482e4bb1af21363f951affff7ee3fefeab
Introduce HardwareRendererObserver to isolate the android.graphics
package from the android.view package. The native code that
interacts with the observer was also moved from libandroid_runtime to
libandroid_graphics to keep it within the confines of the UI Rendering
module.
Bug: 137655431
Test: CtsUiRenderingTestCases
Change-Id: Ibccecbeda0c4d9501d86514a53eb98548233ba6a
Bug: 135133301
Test: Idf64474f28c0bf3f77616a31d843d84fbfd570ab
If the specified crop Rect is empty or unsorted, throw an
IllegalStateException, like we do if the Rect does not fit in the target
size.
This is a change in behavior to make it more consistent. Here are the
specific behavior changes:
- an empty crop rect was previously supported in all cases, but would
result in a zero width and/or height Bitmap/Drawable. If one
dimension is non-zero, it still affects layout, though nothing is
drawn. This is not useful, so the new Exception is more helpful. (It
is also more consistent with setTargetSize, which throws an
IllegalArgumentException for non-positive dimensions.)
- a negative width or height in decodeBitmap, or on a static image in
decodeDrawable, previously threw an IOException when trying to call
SkBitmap::setInfo with a negative width or height. Throwing an
IllegalStateException is more consistent with other invalid crop rects
- a negative width or height in decodeDrawable on an animated image
previously resulted in an AnimatedImageDrawable with a negative
intrinsic width and/or height. When passed to an ImageView, this
dimension ends up being 1. Again, this does not seem useful.
Change-Id: I15d2f77125799413eaf55d417e98ff34599e2eb4
We want to eventually migrate some of these APIs to be @SystemApi for mainline modules.
The #dumpDebug name is more appropriate than #writeToProto.
Bug: 142279786
Test: Manual
Change-Id: I60793e91cedf6b720d4ecef6a8484f4fed4ff30f
Add RuntimeShader hidden API, which calculates pixel output with
a fragment shader running on GPU.
Extend ColorFiltersMutateActivity HWUI test to use new API and
show how to animate uniforms on UI thread.
Test: Updated HwAccelerationTest
Change-Id: Ia26e44259b12099924facba250880cbbd9be21c7
Bug: 143231863
Test: Infeasible?
Previously we compared with "==", which requires that the two String
objects be the same to return true. We want to return true if the two
Strings are logically equal, even if they are different objects.
Prior to this commit, we may have accidentally called
openAssetFileDescriptor when we should have called
openTypedAssetFileDescriptor.
Change-Id: I9229039b752bafa9a9b85b914a62093dff1eec34
Adds a new creator method to accept a Uri and set an internal flag for
Adaptive bitmap, and return adaptive bitmap drawable on loadDrawable().
Bug: 142831407
Test: atest IconTest
Change-Id: Iefee1aaa154a47fc9e5ed1e1c03587a3c8fb6da9
add parameter descriptions for index and count in drawTextOnPath
fix a couple of typos
test: make ds-docs
Bug: 36969777
Change-Id: I7c451fac4468fb2066b9b29a321fad57785a8a36
Updated DrawableWrapper to provide an implementation
of Drawable#jumpToCurrentState to call into the
internal Drawable's implementation
Test: Added CTS test to DrawableWrapper
Bug: 142867050
Change-Id: Ifd095c3174da2e240fdfe4a27cfe081db16a6db5
region of GradientDrawable even if none was defined
Fixed issue where solid black would be applied through
modulated default alpha value if both solid and gradient
colors were not applied to the gradient.
Test: Added CTS test
Bug: 142733137
Change-Id: Iecb7010f6d318cc962113528aac694b0de47d9dd
There are multiple problems here:
- Java Font.equals and hashCode doesn't look at locale list. Due to this
issue, the CTS tests have been passing unexpectedly.
- The null pointer check in the AFont_getLoacle was inversed. Should
return only when it is non-null.
- Looks like we cannot get the parent's attribute which always returns
null. Instead, read the "lang" attribute when we read the family tag.
Bug: 139201432
Test: atest NativeSystemFontTest
Test: atest TypefaceEqualsTest
Change-Id: I0514847bbf46a73358afab374ccfce2db09b2ec0
Bug: 140961740
Test: TODO
We already catch an FNF and attempt to open the file as an InputStream.
Do the same if null is returned.
I haven't figured out a way to make assetFd set to null and yet opening
an InputStream succeeds, so this is untested.
Change-Id: Iabd05db714bc693ead2dc8cc4c0b46fef9f33d5a
If the Gradient angle is negative after
modding by 360, maintain the previous platform
behavior of TOP_BOTTOM oreintation instead of
attempting to wrap it
Test: Added CTS test to verify various negative
angle measurements
Bug: 142111195
Change-Id: Id9c050a9e15717bfaff331c6a37cb34cbce0f060
Add support for ViewRootImpl submitting buffers using
BLAST and put this support behind a disabled-by-default
FLAG.
Bug: 135786080
Change-Id: Ia3f205e34db9f9aa574c9c2e2c499dd3046af220
Bug: 135133301
Test: Iadbd8cf3b69a150b9e38ad556392346e1bb27084
WEBP does not give clients explicit control of how to do their WEBP
encode. Add new formats that do. Update the docs for the existing
formats (and the new ones) to explain more precisely how quality is
interpreted.
Change-Id: I9583903c21ab2048fed8e7ed501ee8377ea5ba36
Fixed issue where GradientDrawable orientation had diverged
from the default behavior. Ensured that orientation by default
is configured to LEFT_RIGHT for xml defined GradientDrawables
and programmatically defined GradientDrawables have the
same default orientation of TOP_BOTTOM.
Refactored previous logic that would keep both the mAngle
parameter used in xml inflation and the mOrientation parameter
that is used to configure the angle of the gradient to no longer
keep these 2 values in sync.
Test: Added CTS test to verify orientation for xml and programmatically
defined GradientDrawables
Bug: 140835351
Bug: 139822941
Change-Id: I594496afe48d04d108053bf284e92bbfd3591fa3
This reverts commit d31d096720.
Reason for revert: Although this change fixed the behavior change for for creation of
GradientDrawables defined in xml, the default value for GradientDrawables defined
programmatically is different. The default orientation for GradientDrawables defined
in xml is LEFT_RIGHT, however, the default orientation for GradientDrawables defined
programmatically is TOP_BOTTOM. Since a fix for AAPT has been made to automatically
insert an angle measurement of 0 if one is not defined, we can revert this CL and target
a proper fix in master.
Change-Id: Ib8983386832fb25f53b5e68e76e9d41d9d26fec9
