I mount my NavigationView dynamically like this:
#Override
protected void onPostCreate(Bundle savedInstanceState) {
//nvDrawer is mount
Menu menu = nvDrawer.getMenu();
for (MyMenuItem kmi : menus.values()) {
menu.add(kmi.getText());
MenuItem mi = menu.getItem(menu.size() - 1);
mi.setTitle(kmi.getText());
Drawable dIcon =
getResources().getDrawable(getResources()
.getIdentifier(S
tring.valueOf(kmi.getIconId()), "drawable", getPackageName()));
mi.setIcon(dIcon);
}
}
So, I debug and the dIcon is setted, but the icon there appears in running app.
Every menus appears, but none icon appears, just silver rectangles.
P.S: My icons are png images.
I'm waiting.
Dimmy,
If you're running your code on Android 3.0+, the icons in the menu are not shown by design. This is a design decision by Google.
You can read more about it below on Android developers blog.
Hope it helps.
http://android-developers.blogspot.in/2012/01/say-goodbye-to-menu-button.html
A few days ago, I decided to make an Android app with a Navigation Drawer, in Eclipse (NOT Android Studio) using Material Design. It came preloaded with 3 default items in the Navigation Drawer. Since I needed more, I added some in strings.xml and added them in the array in NavigationDrawerFrament.java, and they started appearing in the Navigation Drawer.
The problem is, the names in the Action Bar didn't change. Let's assume that they came preloaded as 'thingOne', 'thingTwo' and 'thingThree', and I added 'thingFour' and 'thingFive'. If I click on thingOne, the text in the Action Bar changes to 'thingOne'. Same with thingTwo and thingThree. But if I clicked on thingFour after thingOne, then the text in the Action Bar remains as thingOne.
I need to change the text in the Action Bar. Please help soon.
Edit:
The code in that is executed on item select is this:
public boolean onOptionsItemSelected(MenuItem item) {
if (mDrawerToggle.onOptionsItemSelected(item)) {
return true;
}
if (item.getItemId() == R.id.action_example) {
Toast.makeText(getActivity(), "Coming soon.", Toast.LENGTH_SHORT).show();
return true;
}
return super.onOptionsItemSelected(item);
}
Note: R.id.action_example refers to a search function I am currently working on; hence, the 'Coming soon.'
By "Action bar name", you mean Activity name displayed in the Action Bar ? If so you might want to check out :
getActionBar().setTitle("Title");
Or if you're targeting API <= 10 :
getSupportActionBar().setTitle("Title");
How to Implement NavigationDrawer icon like in Android L.
I have updated play store app where i can see icon of navigation drawer something like this:
Here big change is the new “hamburger” button, which is bigger, spaced off from the left edge, and no longer has a category icon. Clicking on it opens up the side menu, and the icons turns into a back arrow with a smooth little animation.
Is it possible to implement the same in lower versions of android ?
Any example or sample ?
Edit - October 18th
As of October 17th it's not necessary to use a Third-Party library for this anymore. Google just released the Android 5.0 SDK along with a new v7 appcompat library. The new v7 appcompat added support for material design user interfaces and updated ActionBarDrawerToggle, which contains the menu-to-arrow animation.
So in order to have the Burger-to-Arrow animation in your NavigationDrawer you just have to use the new ActionBarDrawerToggle (import android.support.v7.app.ActionBarDrawerToggle) and the NavigationDrawer like before (see Developer Training).
While the ActionView by markushi gives you the desired transformation between the burger-icon and the arrow it lacks the option for being used in the "Standard" ActionBar. For this you should consider to use the library material-menu by balysv.
The usage of the library itself may be straightforward, but if you've used the ActionBarDrawerToggle previously you should remove it.
Following just a little "How to" for everyone who wants to use the DrawerLayout without the ActionBarDrawerToggle but with the MaterialMenu library:
1 - Add library in build.gradle file
dependencies {
//...
compile 'com.balysv.materialmenu:material-menu:1.3.1'
}
2 - Init MaterialMenuIcon
materialMenu = new MaterialMenuIcon(this, Color.WHITE, MaterialMenuDrawable.Stroke.THIN);
3 - Set DrawerListener and change IconState accordingly
mDrawerLayout.setDrawerListener(new DrawerLayout.DrawerListener() {
#Override
public void onDrawerSlide(View drawerView, float slideOffset) {
materialMenu.setTransformationOffset(
MaterialMenuDrawable.AnimationState.BURGER_ARROW,
isDrawerOpened ? 2 - slideOffset : slideOffset
);
}
#Override
public void onDrawerOpened(View drawerView) {
isDrawerOpened = true;
}
#Override
public void onDrawerClosed(View drawerView) {
isDrawerOpened = false;
}
});
Note: isDrawerOpened should be global variable
4 - Open/Close NavDrawer
Add this to onOptionsItemSelected(MenuItem item)
if(item.getItemId() == android.R.id.home) {
if (mDrawerLayout.isDrawerVisible(GravityCompat.START)) {
mDrawerLayout.closeDrawer(GravityCompat.START);
} else {
mDrawerLayout.openDrawer(GravityCompat.START);
}
}
Note: Since we're not using the ActionBarDrawerToggle we have do this on our own.
Further steps like saving the state of the MenuIcon can be found here.
Edit
As mentioned by Piyush Kukadiya MaterialMenu uses NineOldAndroids for compatibility reasons. If you don't want this because your app only supports API-Level 11 and above here's what you roughly need to do (though I'd say it’s probably not worth the hassle - furthermore you'll only save 39kb):
Download the Library from GitHub
Import it as a new module to your Project
Set it as a dependency to your app-module
Remove compile 'com.nineoldandroids:library:2.4.0' from build.gradle file of the library and set minSdk to 11
Remove any import referecing com.nineoldandroids.*
As Google release the new support library Android Support Library, revision 21,you can see how to achieve the effect in ActionBarDrawerToggle this page.
I've installed successfully Sherlock's Action Bar and the 2 items i've added are placed well!
But it appears that Sherlock has not replaced the default android action bar, and i always get an android image on the left :/
How can i remove it? Or replace it?
I want to place on the left my app's name - with some action - but i can't and don't know how, if Sherlock does not work well.
Please help! :(
Here is how you can set an icon and a title, and listen for the item click:
// in onResume
ActionBar bar = getSupportActionBar();
bar.setTitle( "My App Name" );
bar.setHomeButtonEnabled( true );
bar.setIcon( R.drawable.your_icon );
// later
#Override
public boolean onMenuItemSelected( int featureId, MenuItem item )
{
if( android.R.id.home == item.getItemId() )
{
// do your stuff here
return true;
}
return super.onMenuItemSelected( featureId, item );
}
You can change the icon with actionbar.setIcon() or you can remove it completely by using actionbar.setDisplayShowHomeEnabled(false).
Actionbarsherlock is only a wrapper. On Android versions where the native Actionbar is available, you will see the native one, on lower android versions you will see the actionbar provided by ABS.
I'd like to have all of the menu items that don't fit into the ActionBar go into the overflow menu (the one that is reached from the Action Bar not the menu button) even on devices that do have a Menu button. This seems much more intuitive for users than throwing them into a separate menu list that requires the user to jump from a touch(screen) interaction to a button based interaction simply because the layout of the ActionBar can't fit them on the bar.
On the emulator I can set the "Hardware Back/Home Keys" value to "no" and get this effect.
I've searched for a way to do this in code for an actual device that has a menu button but can't fine one. Can anyone help me?
You can also use this little hack here:
try {
ViewConfiguration config = ViewConfiguration.get(this);
Field menuKeyField = ViewConfiguration.class.getDeclaredField("sHasPermanentMenuKey");
if (menuKeyField != null) {
menuKeyField.setAccessible(true);
menuKeyField.setBoolean(config, false);
}
} catch (Exception ignored) {
}
Good place to put it would be the onCreate-Method of your Application class.
It will force the App to show the overflow menu. The menu button will still work, but it will open the menu in the top right corner.
[Edit] Since it has come up several times now: This hack only works for the native ActionBar introduced in Android 3.0, not ActionBarSherlock. The latter uses its own internal logic to decide whether to show the overflow menu. If you use ABS, all platforms < 4.0 are handled by ABS and are thus subjected to its logic. The hack will still work for all devices with Android 4.0 or greater (you can safely ignore Android 3.x, since there aren't really any tablets out there with a menu button).
There exists a special ForceOverflow-Theme that will force the menu in ABS, but apperently it is going to be removed in future versions due to complications.
EDIT: Modified to answer for the situation of physical menu button.
This is actually prevented by design. According to the Compatibility Section of the Android Design Guide,
"...the action overflow is available from the menu hardware key. The resulting actions popup... is displayed at the bottom of the screen."
You'll note in the screenshots, phones with a physical menu button don't have an overflow menu in the ActionBar. This avoids ambiguity for the user, essentially having two buttons available to open the exact same menu.
To address the issue of consistency across devices: Ultimately it's more important to the user experience that your app behave consistently with every other app on the same device, than that it behave consistently with itself across all devices.
I use to workaround it by defining my menu like this (also with ActionBarSherlock icon used in my example):
<menu xmlns:android="http://schemas.android.com/apk/res/android" >
<item
android:id="#+id/menu_overflow"
android:icon="#drawable/abs__ic_menu_moreoverflow_normal_holo_light"
android:orderInCategory="11111"
android:showAsAction="always">
<menu>
<item
android:id="#+id/menu_overflow_item1"
android:showAsAction="never"
android:title="#string/overflow_item1_title"/>
<item
android:id="#+id/menu_overflow_item2"
android:showAsAction="never"
android:title="#string/overflow_item2_title"/>
</menu>
</item>
</menu>
I admit that this may require manual "overflow-management" in your xml, but I found this solution useful.
You can also force device to use HW button to open the overflow menu, in your activity:
private Menu mainMenu;
#Override
public boolean onCreateOptionsMenu(Menu menu) {
// TODO: init menu here...
// then:
mainMenu=menu;
return true;
}
#Override
public boolean onKeyUp(int keycode, KeyEvent e) {
switch(keycode) {
case KeyEvent.KEYCODE_MENU:
if (mainMenu !=null) {
mainMenu.performIdentifierAction(R.id.menu_overflow, 0);
}
}
return super.onKeyUp(keycode, e);
}
:-)
If you are using the action bar from the support library (android.support.v7.app.ActionBar), use the following:
<?xml version="1.0" encoding="utf-8"?>
<menu xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:yorapp="http://schemas.android.com/apk/res-auto" >
<item
android:id="#+id/menu_overflow"
android:icon="#drawable/icon"
yourapp:showAsAction="always"
android:title="">
<menu>
<item
android:id="#+id/item1"
android:title="item1"/>
<item
android:id="#+id/item2"
android:title="item2"/>
</menu>
</item>
</menu>
This kind of method is prevented by the Android Developers Design System, but I found a way to pass it:
Add this to your XML menu file:
<item android:id="#+id/pick_action_provider"
android:showAsAction="always"
android:title="More"
android:icon="#drawable/ic_action_overflow"
android:actionProviderClass="com.example.AppPickActionProvider" />
Next, create a class named 'AppPickActionProvider', and copy the following code to it:
package com.example;
import android.content.Context;
import android.util.Log;
import android.view.ActionProvider;
import android.view.MenuItem;
import android.view.MenuItem.OnMenuItemClickListener;
import android.view.SubMenu;
import android.view.View;
public class AppPickActionProvider extends ActionProvider implements
OnMenuItemClickListener {
static final int LIST_LENGTH = 3;
Context mContext;
public AppPickActionProvider(Context context) {
super(context);
mContext = context;
}
#Override
public View onCreateActionView() {
Log.d(this.getClass().getSimpleName(), "onCreateActionView");
return null;
}
#Override
public boolean onPerformDefaultAction() {
Log.d(this.getClass().getSimpleName(), "onPerformDefaultAction");
return super.onPerformDefaultAction();
}
#Override
public boolean hasSubMenu() {
Log.d(this.getClass().getSimpleName(), "hasSubMenu");
return true;
}
#Override
public void onPrepareSubMenu(SubMenu subMenu) {
Log.d(this.getClass().getSimpleName(), "onPrepareSubMenu");
subMenu.clear();
subMenu.add(0, 1, 1, "Item1")
.setIcon(R.drawable.ic_action_home).setOnMenuItemClickListener(this);
subMenu.add(0, 2, 1, "Item2")
.setIcon(R.drawable.ic_action_downloads).setOnMenuItemClickListener(this);
}
#Override
public boolean onMenuItemClick(MenuItem item) {
switch(item.getItemId())
{
case 1:
// What will happen when the user presses the first menu item ( 'Item1' )
break;
case 2:
// What will happen when the user presses the second menu item ( 'Item2' )
break;
}
return true;
}
}
Well I think that Alexander Lucas has provided the (unfortunately) correct answer so I'm marking it as the "correct" one. The alternative answer I'm adding here is simply to point any new readers to this post in the Android Developers blog as a rather complete discussion of the topic with some specific suggestions as to how to deal with your code when transitioning from pre-level 11 to the new Action Bar.
I still believe it was a design mistake not have the menu button behave as a redundant "Action Overflow" button in menu button enabled devices as a better way to transition the user experience but its water under the bridge at this point.
I'm not sure if this is what you're looking for, but I built a Submenu within the ActionBar's Menu and set its icon to match the Overflow Menu's Icon. Although it wont have items automatically sent to it, (IE you have to choose what's always visible and what's always overflowed) it seems to me that this approach may help you.
In the gmail app that comes with ICS pre-installed, the menu button is disabled when you have multiple items selected. The overflow menu is here "forced" to be triggered by the use of the overflow button instead of the physical menu button. Theres a 3rd-party lib called ActionBarSherlock which lets you "force" the overflow menu. But this will only work on API level 14 or lower(pre-ICS)
If you use Toolbar, you can show the overflow on all versions and all devices, I've tried on some 2.x devices, it works.
Sorry if this problem is dead.
Here is what I did to resolve the error. I went to layouts and created two ones containing toolbars. One was a layout for sdk version 8 and the other was for sdk version 21. On version 8, I used the android.support.v7.widget.Toolbar while I used android.widget.Toolbar on the sdk 21 layout.
Then I inflate the toolbar in my activity. I check the sdk to see if it was 21 or higher. I then inflate the corresponding layout. This forces the hardware button to map onto the toolbar you actually designed.
For anyone using the new Toolbar:
private Toolbar mToolbar;
#Override
protected void onCreate(Bundle bundle) {
super.onCreate(bundle);
mToolbar = (Toolbar) findViewById(R.id.toolbar);
setSupportActionBar(mToolbar);
...
}
#Override
public boolean onKeyUp(int keycode, KeyEvent e) {
switch(keycode) {
case KeyEvent.KEYCODE_MENU:
mToolbar.showOverflowMenu();
return true;
}
return super.onKeyUp(keycode, e);
}