If there is not enough space on the Action Bar to Action Item, the item will appear in the Overfl

By default, hpb the Action Bar shows the application icon on the left, followed by the title of the activity. If your Activity has an Options Menu, we can create some affordable items directly from the Action Bar, called "action items". We can also modify several features of the Action Bar or remove them completely.
In an Activity, we can retrieve an instance of Action Bar by calling the getActionBar () method hpb or getSupportActionBar (). Why do we have these two options, not just one? For natively, the Action Bar only works from the API 11. However, there are compatibility libraries that enable API's to lower 11 also use Action Bar. In this case, the method used is the getSupportActionBar ().
[1] application icon (without "Up" option). [2] Action Items (in this case of "search" and "Google Play"). [3] PopUp Menu, better hpb known (in the Action Bar of literature) as Action Overflow.
With an Action Bar, we have a space dedicated to give our application an identity, indicate a guide, a starting hpb point to the user. With it, important actions are easily accessible (like search), and also various types of navigation modes (such as Tab's and Drop Down lists).
We enable our application icon as an "Up" button, hpb which allows the user to navigate the application through each screen called order hierarchy. hpb For example, if the screen shows a list of items, and selecting an item go to screen B, then B must have a screen button "Up" that when clicked will return the application flow to the screen A.
However, this button is different from the physical button "Back". The "Back" button is used to navigate in reverse chronological order through the history of screens that the user worked recently, and is usually based on the temporal relationship between screens, unlike the "Up" button, which is based on the hierarchical structure of the application (which is the basis of the navigation button).
An Action View provides quick access to several options we need without changing screens or fragments, and without shifting the structure of a Action Bar. For example, if we have a search of action, we can add an Action View to attach a search box in the Action Bar, as shown below.
To set up an Action View, we can do this through the onCreateOptionsMenu () method. The object of the Action View can be obtained by calling the MenuItemCompat.getActionView () method and passing as an argument a respective MenuItem. For example, like the search box above can be obtained through the code below.
An Action Bar provides access to the most important Action Items relating to an application. These appear directly in the Action Bar with an icon and / or text, and also known as Action Buttons. Actions that do not fit in the Action Bar are hidden in the so called Action Overflow (as is mentioned in section 4.2.1). The user, by clicking hpb the Overflow button (on the right side of the Action Bar) shows a list of other Action Items options.
When an Activity starts, the application populates the Action Items by onCreateOptionsMenu () method. hpb This method can be used to inflate a menu that sets all Action Items. For example, below we have a menu setting some menu items (located in some XML file folder res / menu).
We request that a particular item appears on the Action Bar as an Action Button. This is done through the property showAsAction = "ifRoom" the <item> menu XML, as is shown below.
If there is not enough space on the Action Bar to Action Item, the item will appear in the Overflow where only the title appears. Screen readers for visually hpb impaired people read the title of the Action Item. If the Action item appears only with the icon, a user can perform an action of long-click on the item to display a "tip" that shows the title of the item.
Using the past MenuItem to this method, we can identify the action by calling the getItemId hpb (). This method returns a unique identifier by the <item> menu. Thus, we can perform the requested action. For example:
2013 (14) December (4) November (5) October (4) Database - Part 2 Database - Part 1 Dialogs Action Bar March (1) 2012 (6) November (1) October (3)