--- title: Merchandise and Donations layout: default ---
Have a question that is not listed on this page? See the "Direct Contact" section of the support page.
What action bar library is used on pre-3.0 devices? |
The widget is a custom implementation that was purpose-built to mimic the API, functionality, and look of the native action bar on 3.0+ devices. The basis for the widget was work done on Johan Nilsson's Android-ActionBar library. The first two versions of ActionBarSherlock used his library directly for support on pre-3.0 devices and without his work the current version of the library would not be possible. |
---|---|
What API level should I target if I want to use the library? | The library itself must be built against Android 3.2 (API level 13). Your project should be built using the latest version of the SDK as possible (it is best to try and use the same version as the library). This is not a requirement, however, and you may build against any version of the SDK that is Android 3.0 (API level 11) or newer. |
Why do I have to target at least API level 11 or newer? | Targetting API level 11 or newer will cause Android to automatically add the native action bar when run on devices using Android 3.0+. Since you will be compiling against new APIs but your app will likely be run on devices with older versions of Android extra care must be taken to either avoid using or properly check and call any methods that were introduced after your minimum SDK version. |
Why do action modes not work on pre-3.0 devices? | Action mode support is still being worked on for pre-3.0 devices and will be released with a future version of the library. |
Why doesn't the logo defined on the activity/application entry in the manifest get displayed? | Despite there being support for loading the logo for activities and applications since API level 9, the underlying implementation in Android is broken and does not work at all. In order to specify a logo on these platforms you should use the abLogo attribute in a custom theme. |
List and tab navigation hide the title on pre-3.0 devices. Can this be changed? | Due to the relatively small space to display items on phones, this cannot currently be changed. Future versions of the library will behave more like the native action bar on larger displays (e.g., Nook Color, Archos 101). |
Can you add functionality *X* to the action bar? | As a general rule, no. If the native action bar on Android 3.0+ does not support it then it will not be supported by this library. |
Why is ActionBarSherlock a library project whereas the original compatibility library is only a .jar ? |
ActionBarWatson, the custom action bar implementation within ActionBarSherlock for pre-3.0 devices, relies on styles, themes, layouts, and drawables in order to display properly. Due to the limitations of Android and .jar files, it can not be accomplished any other way. |
I found a bug, what should I do? | See the support page and create an issue on GitHub, post to the Google Group, or contact me directly. Or do all three! The worst thing you can do is to not report it. Please try to include as much information as possible in your report. |
What causes the following error: Binary XML file line #8: You must supply a layout_height attribute ? |
You application or activity is not using a theme from the application. See the "Parent Themes" section of the theming page. |
Do I need to include the .jar file for the Android compatability library when using ActionBarSherlock? |
No. ActionBarSherlock is built on top of the Android compatability library and comes bundled with its class files. Including the .jar will result in a very large number of compile-time errors. |
I use progaurd. Are there any lines I should include to ensure functionality of the library? |
Add the following lines:
|