History log of /frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
c39d9c75590eca86a5e7e32a8824ba04a0d42e9b 25-Aug-2016 Alan Viverette <alanv@google.com> Add @RestrictTo(GROUP_ID) annotations to match @hide docs annotations

Also removes some unnecessary @hide annotations on classes that wouldn't
have shown up in docs anyway due to package/private visibility or NO_DOCS.

Bug: 27937193
Change-Id: Iab127a5a3ce57a2d61965d3cef782621eb3859f5
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
96a3a5a841741fddc3773f35a22e31cded6bbdd8 06-Sep-2016 Aurimas Liutikas <aurimas@google.com> Remove all the extra accessor methods added by javac in support-design.
am: 657ea1100f

Change-Id: I762e3378d1c7e82139e9f04c3f750324ffd9851c
657ea1100fee4750f148f9d0dcb7e7e2028f105e 25-Aug-2016 Aurimas Liutikas <aurimas@google.com> Remove all the extra accessor methods added by javac in support-design.

Change private methods to be package protected to avoid extra methods
that get added to be able to access them from inner classes.

This CL saves 138 methods in our jar.

Bug: 31075707
Change-Id: I9ee192652fe005957e28ccfe35c9707be242aac1
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
6ff96f58e00664a867b9f9e8e900ca190a82ebf4 23-Aug-2016 TreeHugger Robot <treehugger-gerrit@google.com> Merge "Fix usages of deprecated methods in support-design code." into nyc-mr1-dev
7b75d53b8e5584895595f801256a3d63bb68148a 23-Aug-2016 Aurimas Liutikas <aurimas@google.com> Fix usages of deprecated methods in support-design code.

Bug: 30074170
Bug: 31017538
Change-Id: Ib62709f853ca13db889d91688c30c97ee48fbe01
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
47082c30c630c34829439a9eecd1cf7e8d255a86 23-Aug-2016 Aurimas Liutikas <aurimas@google.com> Fix all usages of deprecated setBackgroundDrawable.

- Adds ViewCompat#setBackground that will call setBackgroundDrawable
or setBackground depending on the version.
- Replaced usages of setBackgroundDrawable with this ViewCompat version.

Bug: 30074170
Change-Id: I756c8558608da752acd6f3ca7121114d3cd1416a
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
252919d15a87bb0c42c9c744fef560aa83e88b0e 24-Jun-2016 Yuichi Araki <yaraki@google.com> NavigationView allows manual tints of icons

Bug: 27739955
Change-Id: Ic38216595b99726b580b02a506b974ab303c9924
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
7c4c746823d82cedc3555ecbcb3c90142337ed65 27-Jun-2016 Yuichi Araki <yaraki@google.com> Fix NavigationView talkback

NavigationView should not announce the checked states of its
non-checkable items.

Bug: 29738248
Change-Id: Iff9783e4002f91d8db2682d486650209bc50e142
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
f3865fbd67715b07d43da357dea742edf3bf9913 15-Jun-2016 Yuichi Araki <yaraki@google.com> NavigationView supports full-width custom views

Bug: 28992790
Change-Id: I5dacd8e859badabdc7f35c40d4cd82c017a868b9
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
6759b1021d8198ad1d239bb30e5a102b99624bce 25-Feb-2016 Adam Lesinski <adamlesinski@google.com> Build support libs with AAPT2

Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.

Ex:

LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4

Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.

This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.

We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.

Bug:25958912
Change-Id: I6577a91e4d428dd29fecaa86a26be43d4da8310c
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
57f39186667b8acef1a0ebeda585c357a751a8b3 02-Apr-2016 Adam Lesinski <adamlesinski@google.com> Revert "Build support libs with AAPT2"

This reverts commit 66b8608151c5923de3c9877bc03218d83f6b3beb.

Change-Id: I2178c0336bef8386e1f36ff3816b6dbf1e6a64d0
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
66b8608151c5923de3c9877bc03218d83f6b3beb 25-Feb-2016 Adam Lesinski <adamlesinski@google.com> Build support libs with AAPT2

Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.

Ex:

LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4

Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.

This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.

We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.

Bug:25958912
Change-Id: I5235b73ac68f2050d089aefc3163901ff80f2d46
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
4ac91fa3f14db2f25345595fb921497c11d4e5c0 31-Mar-2016 Adam Lesinski <adamlesinski@google.com> Revert "Build support libs with AAPT2"

This reverts commit 0dac8d82e2a249d7c9c42ab259389e11cac15400.

Change-Id: I830fb18162b6eea8dde9e38f9dc39b02449ec846
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
0dac8d82e2a249d7c9c42ab259389e11cac15400 25-Feb-2016 Adam Lesinski <adamlesinski@google.com> Build support libs with AAPT2

Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.

Ex:

LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4

Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.

This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.

We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.

Bug:25958912
Change-Id: I71bff080ff2694aa3df1c8a67d933e2daab0f245
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
66698bb15ba0f873aa1c2290cc50d6bb839a474a 26-Oct-2015 Chris Banes <chrisbanes@google.com> Flatten AppCompat class hierarchy

This allows us to do two things:

1) Move away from using public @hidden classes
everywhere.
2) Workaround silly OEM bugs.

BUG: 18218511

Change-Id: I7582e242c7564c32feeb044fc9eff6bfb5c56536
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
e7c47b46298c70ab4eb7945e27904adf9fd99ea9 29-Sep-2015 Yuichi Araki <yaraki@google.com> Fix NPE in setIcon

This can happen for some implementation of Drawable that returns null
for getConstantState().
Bug: 24485410

Change-Id: I182a9d9a1fd20a8afe860f567757ea9746aaa4af
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
64bcb674cc45ab712a591d4f540d5c13404f3b83 03-Sep-2015 Yuichi Araki <yaraki@google.com> Revert "Revert "Use RecyclerView for NavigationView""

This reverts commit ca2f07c9cc83b98d73a18da7177044ee147ffb94.

Change-Id: I7c19c2f84fc4b520b8a1951729c40a1f9ac1435f
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
ca2f07c9cc83b98d73a18da7177044ee147ffb94 01-Sep-2015 Chris Banes <chrisbanes@google.com> Revert "Use RecyclerView for NavigationView"

This reverts commit e7b2c26d2ffadc94dc6ee043ab12e03201e1bf95.

Change-Id: I1c7ec7629a08566dd4a17431a857e36961ba8270
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
e7b2c26d2ffadc94dc6ee043ab12e03201e1bf95 25-Aug-2015 Yuichi Araki <yaraki@google.com> Use RecyclerView for NavigationView

Replace ListView with RecyclerView. This does not change any public
APIs.

Change-Id: I618360f0267c74692dd2e4489455b845c379d52c
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
36d347c02fa8da71ccd69634484be8156fa0085b 14-Jul-2015 Yuichi Araki <yaraki@google.com> NavigationView now supports app:actionLayout

The specified layout is inflated as an extra item in the menu row.

Bug: 22837324
Change-Id: Iaa0921c45395dd779429052019761e59d66c34be
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
a577676a64e5353b8ec927117151aa6be84adf66 23-Jun-2015 Chris Banes <chrisbanes@google.com> Prefix design lib resources to try and avoid conflicts

BUG: 21363917
Change-Id: I770a01618ac8fefae6d82d1640ccf313111e38e8
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
1a542ba7235ec038f7ec1ac0ed65f35d29f5c952 15-Jun-2015 Yuichi Araki <yaraki@google.com> Fix issues with Drawable states in NavigationView

- Background drawable is properly rendered now
https://code.google.com/p/android/issues/detail?id=176570
- Icon tinting properly works on Gingerbread now
https://code.google.com/p/android/issues/detail?id=176133

Change-Id: I6485a3fbeb7076151233cebccc0b4478a0210cd3
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
a63940ca14cd3ad9620e94f709930bb968525c57 01-May-2015 Chris Banes <chrisbanes@google.com> Tidy up styling and tinting in NavigationView

Currently there is no way to set a different tint/color
for the text and icon. This icon splits them up and tidies
up some of the internal state.

Change-Id: I5d81f19dddf2df6cfc983fc2a60b2353a780d522
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
a5081dfb26b3664d97d5fe09b9b6a9c9667e0e9f 19-Feb-2015 Yuichi Araki <yaraki@google.com> Rename NavigationDrawerView to NavigationView

Change-Id: I639fbb4754add5d72f5baaca6728fc1348e256e0
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
d3ee2c7d22c0cb204ea9077fa9e64511266d6799 10-Feb-2015 Yuichi Araki <yaraki@google.com> Add selection feature to NavigationDrawerView.

The selected item can be marked by MenuItem#setChecked in
onNavigationItemSelected callback. This also takes MenuGroup into
account, that is, NavigationDrawerView highlights only one item in one
MenuGroup.

Also removes an unnecessary separator when a MenuGroup comes at the top
of the menu.

Change-Id: Ia7373bb8b64836de8a0db7552c5304165afa7d64
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
31a49efe2adb59e31611f6871895a3243d835127 30-Jan-2015 Yuichi Araki <yaraki@google.com> Initial implementation of NavigationDrawer

NavigationDrawer can be used inside DrawerLayout (support-v4) to provide
navigation menu. The menu can be populated by XML.

This is just a starting point. It still misses a lot of major features,
including marking current item, account switcher API, and pinning items.

This chnage also adds android.support.v4.widget.TextViewCompat with
setCompoundDrawablesRelative* methods.

This reverts commit e34464da9acbbf5891651addc0983d2d920f5be4.

Change-Id: I54cd343be90588cb1735189deb2100552240fde8
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
e34464da9acbbf5891651addc0983d2d920f5be4 30-Jan-2015 Yuichi Araki <yaraki@google.com> Revert "Initial implementation of NavigationDrawer"

This reverts commit d4bea8be0627dac53fb5907f1f64dddf6147d55e.

Change-Id: Ic36cd74dbd8c0ba9b66fd65b096f60a1957011e9
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java
d4bea8be0627dac53fb5907f1f64dddf6147d55e 14-Jan-2015 Yuichi Araki <yaraki@google.com> Initial implementation of NavigationDrawer

NavigationDrawer can be used inside DrawerLayout (support-v4) to provide
navigation menu. The menu can be populated by XML.

This is just a starting point. It still misses a lot of major features,
including marking current item, account switcher API, and pinning items.

This chnage also adds android.support.v4.widget.TextViewCompat with
setCompoundDrawablesRelative* methods.

Change-Id: Ife8e39de2e2938d246713bb8cd486489be92cd6a
/frameworks/support/design/src/android/support/design/internal/NavigationMenuItemView.java