| 4be3573c7ef2b2ac66717d466c22c1fe97b80a9d |
|
09-Jan-2014 |
Adam Powell <adamp@google.com> |
Update internal action bar layouts for API change
Change-Id: Icce370388ddd78f1b2e4115c94072c9420896f0b
/frameworks/base/core/res/res/layout/action_menu_layout.xml
|
| 141bdb17dd4571f8d9eab85853cae7ca8a179707 |
|
08-Nov-2011 |
Adam Powell <adamp@google.com> |
Fix the action bar menu layout to use the correct divider drawable.
Change-Id: I9f9fe8318cbad3cfe4e34a37204a6c82a2e9a0c6
/frameworks/base/core/res/res/layout/action_menu_layout.xml
|
| 696cba573e651b0e4f18a4718627c8ccecb3bda0 |
|
29-Mar-2011 |
Adam Powell <adamp@google.com> |
Refactor menu internals.
In the old world, MenuBuilder and MenuItemImpl were responsible for
generating views for any presentation of a menu. MenuBuilder needed to
know any types and resources involved, and the implied caching
semantics did not work well for menus presented within AdapterViews.
In the new world, the MenuPresenter interface takes over the
responsibility of generating views or adapters for menu
items. MenuBuilder/MenuItemImpl still provide extra metadata tracking
used by these presenters. Mutiple presenters may be active for a
single menu at a time. All of this remains internal framework
implementation details.
BaseMenuPresenter provides a simple base for presenters that treats
the host MenuView more like an AdapterView. This allows for less
rebuilding of views when items are added/removed.
Callbacks have been restructured. Calls that relate to the menu itself
are still handled by MenuBuilder.Callback, but calls related to a
specific presentation of a menu are handled by MenuPresenter.Callback
objects attached to a MenuPresenter.
Also add API to programmatically set divider options for LinearLayout
and hidden API so that ActionBarView can have finer-grained control
over divider placement.
Change-Id: I2265b86a084279822908021aec20dfbadc1bb56b
/frameworks/base/core/res/res/layout/action_menu_layout.xml
|
| 96675b1df3969f2d313b68f60ed9fa36805db8ce |
|
11-Jun-2010 |
Adam Powell <adamp@google.com> |
Merging ActionBar menu with options menu.
Options menu items may now specify if they would like to appear in the
action bar. Menu items defined in xml may set the showAsAction
attribute to one of "never"(default), "ifRoom", or "always". Action
buttons are populated as follows:
* All showAsAction="always" items become action buttons, even if it
would crowd the navigation area of the action bar.
* If there is space remaining, showAsAction="ifRoom" items are added
until no more will fit comfortably.
Action button click events are now handled by the
onOptionsItemSelected method used by the standard options menu.
The construction of options menus now happens earlier in order to
provide data to the action bar. Activities with an action bar can now
expect to have onCreateOptionsMenu called when activity start-up is
complete.
Activity#invalidateOptionsMenu can be used to force a refresh of menu
items where the previous API would use ActionBar#updateActionMenu.
Change-Id: If52ddf1cf9f6926206bcdeadf42072ea2c24fab9
/frameworks/base/core/res/res/layout/action_menu_layout.xml
|