frameworks_base.git - frameworks

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add @Nullable annotation to the parameter of Object.equals() methods.	Roman Kalukiewicz	2020-10-15	1	-1/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Those annotations could be inferred by some tools (like Kotlin), but the https://checkerframework.org/ doesn't check inherited annotations complaining about all equals() invocations that get nullable argument. The change was generated by running find . -name \*.java \| xargs sed -i 's/public boolean equals(Object /public boolean equals(@Nullable Object /' in the frameworks/base directory and by automatically adding and formatting required imports if needed. No manual edits. Bug: 170883422 Test: Annotation change only. Should have not impact. Exempt-From-Owner-Approval: Mechanical change not specific to any component. Change-Id: I5eedb571c9d78862115dfdc5dae1cf2a35343580
*	Reuse overlay view between two Visibility transitions	Andrey Kulikov	2018-10-18	1	-0/+14
\| \| \| \| \| \| \| \| \| \|	Bug: 31362791 Instead of creating a new screenshot of the view every time previous visibility transition already did it or just added our startView to the overlay we can cache it and apply the animation to the same reused view. So the behaviour is the same(and expected) like in the case when no overlay is used. Test: test added in VisibilityTest Fix in AndroidX: aosp/772713 Change-Id: Iba4ab168722595eb19b9c681649a976462a5532b
*	Made Transitions act only the views that they target.	George Mount	2014-09-12	1	-0/+6
\| \| \| \| \| \| \|	Bug 17465989 Bug 17452585 Change-Id: I2f921e98f68df3d549a370179c0a4488d56923ad
*	Transition API changes from API council recommendations	Chet Haase	2013-09-04	1	-0/+82
	Issue #10460684 KLP API Review: android.view.transition and android.animation Issue #10570740 Transitions: inflate transition targets from xml Change-Id: I7a3f6d3aece2fcafc5efd555d033f79e86635c98