In portrait mode, I have a custom, on-screen keypad for the user to enter data with.
In landscape mode, the user will enter data with the physical keyboard. People with Android phones without physical keyboards will always be in portrait mode - using the custom on-screen keypad. There are two or more text input fields on any given screen in my app - so the user touches them (to focus the text input fields) and then based on the orientation (portrait or landscape) uses either the on- screen keypad or the physical keyboard. I am using EditText input fields - and the above reasoning is why I don't want the soft keyboard to interfere. Should I be using something other than EditText input fields? Any advice? On Jun 24, 12:10 pm, Peli <[email protected]> wrote: > As of SDK 1.5 you can use the InputMethodManager > classhttp://developer.android.com/reference/android/view/inputmethod/Input... > as mentioned in this > blog:http://android-developers.blogspot.com/2009/04/updating-applications-... > > I agree with lbcoder that you should also think of people who have > Android phones without a physicalkeyboard. How would they enter > anything into your input fields? > > Peliwww.openintents.org > > On Jun 24, 8:46 pm, lbcoder <[email protected]> wrote: > > > If you don't want it to show up, don't use input fields. If you use > > input fields, you better damned well allow the user to input data into > > them! > > > What I am saying is basically that there is no reason for you to > > forcibly suppress thekeyboard. > > > On Jun 23, 9:13 pm, Alex B <[email protected]> wrote: > > > > Google recently released Android 1.5, adding a significant feature - > > > thesoftkeyboard- yet they have not provided any information on how > > > to *properly* suppress it. Until 1.5, we've been dealing with the > > > physicalkeyboard, and custom onscreen buttons. As of 1.5, an onscreen > > >keyboardappears when an input field is focused/touched. > > > > It seems to me that the introduction of such a major UI feature should > > > come with ample documentation describing how to deal with it... > > > particularly, how to suppress it. Until now, I have not seen any > > > official documentation about this. There has been some discussion on > > > the dev list, but only hacks have been presented. Indeed, some of the > > > hacks do suppress thekeyboard, but they come with the loss of certain > > > behaviour - functional or aesthetic. > > > > What is needed, is a *clean* way of suppressing thekeyboard. At the > > > very least, on a field-by-field basis... but best would be on an > > > activity or app basis. Actually, ideally, all three methods should be > > > presented. > > > > Personally, I don't want thesoftkeyboardto show up *anywhere* > > > within my app, regardless of activity or EditText text input field. If > > > you know how to do this, or if you know how to get the Android team's > > > attention, please help. > > > > Thank you. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
