Am doing an application in KindleFire 2.0 , in my activity am displaying the application in the full screen mode. But I can still see the soft menu bar. Is there any way to hide the menu bar ? Please let me know.
there's a couple of options - the Fire has a "full screen" mode which leaves a drag handle visible to get the on-screen soft keys back with a single tap, or what they call the ICS full screen mode which hides everything (you tap to bring back the drag handle then tap the drag handle to bring back the menus)
https://developer.amazon.com/sdk/fire/cx-guidelines.html#Fullscreen
Related
My game is set to immersive mode using the Application Config (config.useImmersiveMode = true).
Also, in my game, I implement Input.TextInputListener in order to get some user input. However, when someone activates the TextInputListener, the navigation bar comes up, and stays even after they exit out of the TextInputListener. How would I set it to re-hide the navigation bar whenever the user navigates out of the TextInputListener?
Here is my game so you can see the issue yourself:
https://play.google.com/store/apps/details?id=com.samuel.doubledodge
The TextInputListener should come up the first time you start the game, and you can manually make it come up by pressing the "Change name" button on the Game Over screen.
Thanks
normally when the menu button is pressed , the menu appears from the center bottom of the screen. Is there a way to make it appear from sides.
On Android 3.0 and higher, items from the options menu are presented by the action bar which is standard way to provide access to menus and normally menus appears from top right corner. You should go through this once:
Menus Action Bar
I am in a UX flow conundrum. In the ActionBar http://developer.android.com/design/patterns/actionbar.html, I am tasked to place a 'Next' button similar to that in iOS.
I am aware that Android has no equivalent button for that, is there a suggestion?
I would say it depends on your needs. Generally apps with a need for a Next button put it somewhere near the bottom-right of the screen.
I would personally be against putting it on the ActionBar as some devices handle it differently. Older devices might end up putting it behind the Menu button, and you'd have to be careful not to let it go into the overflow '...' menu as it may be too hidden-away in there (again, depending on your use case).
The other thing to remember is that putting it on the right of the Action Bar suggests that the button on the left of the Action Bar is a 'back' button, which is is not (It's an 'up' button).
I'm thinking more something like this:
I have an app with ListView in it and I added search functionality to it. When I press on EditText and it opens keyboard, it pushes everything in the layout along with it.
Normal layout:
With keyboard:
As you can see; the ad, play button, seekbar are all pushed up along with the keyboard, but I don't want that. Is there a way I can avoid this?
I tried adding this to Manifest file:
android:windowSoftInputMode="stateUnchanged"
But that doesn't work.
You probably want to use "adjustPan".
From the documentation:
The activity's main window is not resized to make room for the soft
keyboard. Rather, the contents of the window are automatically panned
so that the current focus is never obscured by the keyboard and users
can always see what they are typing. This is generally less desirable
than resizing, because the user may need to close the soft keyboard to
get at and interact with obscured parts of the window.
as the title suggests I'm trying to add code to my app which allows the user to click on an item in the action bar menu which then unfolds a drop down menu (spinner class?) containing a few options such as lamp, tv etc. - each with an icon. The user will then be able to select one of these and drag and drop the icon (or an image representing the icon) to the canvas where it is then drawn. What is the best way to go about this?
If you're referring to the ActionBar overflow menu items, then you would have to take a look at the code for the ActionBar in the framework and extend it in your application, but that would firstly require quite a hassle and secondly would break compatibility when changes are made to the ActionBar in new versions of Android.
Also, this goes completely away from what the ActionBar is intended to be. You should only have actions in the overflow menu, not contain elements that directly interact with the Activity content. It's just wrong. Consider redesigning your UI so that you implement the requested featured inside the content view, not on the ActionBar.