Nobody with experience on this? Similar problem?
Am Mittwoch, 22. Mai 2013 11:16:02 UTC+2 schrieb user123:
My soft keyboad doesn't show this button when I focus webview input
fields. Don't find anything about special settings to enable this - am I
missing something? It doesn't appear in any
anyone?
http://25.media.tumblr.com/tumblr_m91o6zlVdr1rstqymo2_500.gif
nobody?
On Wednesday, August 22, 2012 12:00:21 PM UTC-4, Steven Settle wrote:
Hi
I am working on a soft keyboard for android. i have been playing with the
qwerty.xml file of the softkeyboard sample built into the android
I have same issue.I couldn't fix this.If you fix this issue please let me
know.
http://stackoverflow.com/questions/7659570/android-oneditoractionlistener-actionid-give-0-when-i-click-done-key
Here also i created one group .: subject is : Android
OnEditorActionListener() method's actionId give
same problem i also facing i decalre like this , but didn't take acttionId
... why?
final EditText txtQty = new EditText(this);
txtQty.setHeight(1);
txtQty.setLayoutParams(new LayoutParams(LayoutParams.WRAP_CONTENT, 42));
There you go, https://github.com/fr4gus/AndroidSoftKeyboardBug
I uploaded a really simple project, in case someone wants to test it
on their devices :D
-f4
On Jul 5, 2:47 pm, fr4gus fggar...@gmail.com wrote:
Thank you all,
and setting windowSoftInputModem stateHidden solves the problem. I'm
Add stateHidden to the activity's manifest entry under
windowSoftInputMode.
On Jul 4, 9:35 pm, fr4gus fggar...@gmail.com wrote:
I'm able to replicate a unusual issue with EditText. But it doesn't
happen on all devices.
Let's say you have the following layout:
?xml version=1.0
I had similar issues and with some testing found that adding:
getWindow().setSoftInputMode(WindowManager.LayoutParams.SOFT_INPUT_STATE_ALWAYS_HIDDEN);
as the last line of my onCreate() in each class that extends Activity
did the trick. Like you the issue with the soft keyboard popping up
did not
I encountered a similar problem and found with some testing that
adding:
getWindow().setSoftInputMode(WindowManager.LayoutParams.SOFT_INPUT_STATE_ALWAYS_HIDDEN);
as the last line of the onCreate() for each class that extends
Activity did the trick. P.S. I apologize in advance if this post
shows
Thank you all,
and setting windowSoftInputModem stateHidden solves the problem. I'm
still wondering why we should explicitly set this value, is this a
bug?
Kind regards,
-f4
On Jul 4, 2:35 pm, fr4gus fggar...@gmail.com wrote:
I'm able to replicate a unusual issue with EditText. But it doesn't
I have the same problem on HTC Nexus One. But OK on Emulator. Anyone
know why?
On May 25, 3:41 pm, Neilz neilhorn...@gmail.com wrote:
To bring this to the top again...
Yes, I'm having problems with it, the DONE button never appears!
Anyone else have experience with this?
On May 22, 11:10
To bring this to the top again...
Yes, I'm having problems with it, the DONE button never appears!
Anyone else have experience with this?
On May 22, 11:10 pm, Nicholas Johnson metthejohn...@gmail.com wrote:
Are you having problems with the implementation?
Make sure to put an
Are you having problems with the implementation?
Make sure to put an OnEditorActionListener in your EditText and screen for
the IME_ACTION_GO action ID.
Nick
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send
Thanks...but to be honest it doesn't help one bit!
It shows a diagram of exactly what I want, but doesn't actually say
how you achieve it. I've tried a few of the code snippets but nothing
made any difference.
It mentions 'full screen' or 'extract mode' - which I think may be
what I'm after -
Neil,
The link provided by TreKing says that:
With the standard IMEs, you will only encounter this situation when
the screen is in a landscape orientation, although other IMEs are free
to use it whenever they desire. In this case the application window is
left as-is, and the IME simply
You can prevent soft keyboard to show by default either in code or
directly in Android.manifest:
1. In code (the results you get when searching the net always points
to a method that really does not work). I found this in the blog of
http://blog.oneguyinabasement.com/.
Or you can add this to your activity in Android.manifest:
android:windowSoftInputMode=stateHidden
On Aug 14, 2:13 am, jb cona...@gmail.com wrote:
I finally found a solution. I placed the following in OnCreate()
I finally found a solution. I placed the following in OnCreate()
this.getWindow().setSoftInputMode(WindowManager.LayoutParams.SOFT_INPUT_STATE_ALWAYS_HIDDEN);
On Aug 13, 2:15 pm, jb cona...@gmail.com wrote:
Hi,
I have an activity which loads a TableLayout. This is made up of
TextView and
Hi,
The Sony Ericsson X10 emulator is basically only a skin which is put
on top of the standard google emulator, which is why the IME of the
emulator doesn't behave as the IME of the phone.
Kind regards
/Johan
Sony Ericsson Developer Support
On Jul 16, 5:53 pm, Dan Dumont ddum...@gmail.com
Hi,
I was asked to comment why the SonyEricsson emulator doesn't emulate
the IME of the X10 hardware. That is because the X10 emulator is
merely a skin put on top of the default android emulator.
Kind regards
/Johan
Sony Ericsson Developer Support #SEDW
--
You received this message because
can you install wwdiary from the market and confirm the reports of no
decimal key on the phonepad?
I'm interested to know what the screen looks like, can you take a
screenshot? After install, press back to get to main screen, then press
the chicken leg.
put the cursor in the points edittext and
Hi
I had issues with the X10s IME in that it ignored particular IME flags
(http://developer.sonyericsson.com/wportal/devworld/forum?
cc=gblc=en). You might be suffering from a similar issue. I suggest
that you post to the SE forum and ask them directly (they confirmed my
findings).
Off the top
My wife's phone has swipe built in and the phone keypad has all the buttons
I need.
I emailed SE and they seem pretty clueless so far, I've followed up asking
them to direct me to their android development staff, because their android
page just points users to general android help. And their
As per:
http://developer.android.com/reference/android/view/inputmethod/InputMethodManager.html
:
A client application can ask that the system let the user pick a new
IME, but can not programmatically switch to one itself.
My point about Swype and Swiftkey is that they may also not handle
your
No, I don't have a sony phone and the emu doesn't have their IME...:(
Just trying to address some complains that my users are having.
On Wed, Jul 14, 2010 at 3:38 PM, jamesc jame...@gmail.com wrote:
As per:
Well, I've got access to an X10 so I'd be willing to test out any
variant apks you want to send my way.
On Jul 15, 2:23 am, Dan Dumont ddum...@gmail.com wrote:
No, I don't have a sony phone and the emu doesn't have their IME... :(
Just trying to address some complains that my users are
On Jun 28, 6:35 pm, YuviDroid yuvidr...@gmail.com wrote:
I found this to work for me:
getWindow().setSoftInputMode(WindowManager.LayoutParams.SOFT_INPUT_STATE_ALWAYS_HIDDEN);
(found
here:http://stackoverflow.com/questions/1109022/how-to-close-hide-the-andr...
)
That doesn't seem to do
Why I am calling this thing a gallery 'widget'? Thats kinda wrong.
Anyway, so I ended up writing my own gallery style view class based on
frame layout. Its pretty much exactly like gallery view but whoa and
behold the edittext's work just fine. Interestingly I noticed that the
default long click
Is anyone able to run the little applications I included above? I
would love to know if it is just me with this problem or if it is a
wider issue with the OS or my code.
I am considering a re-write to ditch the gallery widget, but I kinda
like the UI effect I am getting with the gallery widget; I
Answering my own question here, finally figure out the solution.
In the InputMethodService, override this method:
@Override public void onComputeInsets(InputMethodService.Insets
outInsets) {
super.onComputeInsets(outInsets);
if (!isFullscreenMode()) {
It's not my app being blocked by the keyboard's candidate view. It's
my keyboard's candidate view blocking other apps. And I'd like to fix
the keyboard.
Any other suggestions?
On May 4, 3:05 pm, jamesc jame...@gmail.com wrote:
Take a look at adjustResize and adjustPan:
Take a look at adjustResize and adjustPan:
http://developer.android.com/guide/topics/manifest/activity-element.html#wsoft
On May 2, 8:07 am, ced cedric...@gmail.com wrote:
Hi,
I am playing with the Demo SoftKeyboard the comes with the Android
SDK.
In portrait mode when its candidate view
If you want to keep certain buttons on the screen at all times, set
the android:layout_alignParentBottom=true attribute to a layout of
your buttons. This will force the buttons to move to the top of the
soft keyboard when it is displayed.
On Feb 22, 10:58 pm, wakeup sid wakeupsi...@gmail.com
Answering my own question, had to switch it from a Relative Layout to
a Linear Layout and problem solved. Also, didn't need to define a
Bottom Margin for the Scrollview, but gave it a Layout Weight of 1,
while the table layout with the buttons had the default Layout Weight.
On Feb 19, 10:22 pm,
Hi Todd..
Im also getting the problem like you..yesterday i posted the same question..
How to design a layout when a soft keyboard is opened??
Am having a requirement that when a keyboard is opened my layout view
is to be automatically changed according to the screen size.
Currently in my
AndroidManifest.xml
add ↓
activity android:windowSoftInputMode=adjustPan
http://developer.android.com/intl/ja/guide/topics/manifest/activity-element.html
sorry, i can't english well..
On 1月27日, 午前7:34, HiQuLABS hiqul...@gmail.com wrote:
Any solution to this?
On Jan 12, 4:23 am, Petroleum
If a EditText is created not within the TableLayout, this dynamically
created EditText works as expected. The soft keyboard pops up when
first clicking into the newly created EditText. This must have
something to do with the way the EditText is created inside a new
row. Any ideas? Thanks.
Looks like this is being caused by the call to txt.requestFocus().
Changing to txt.requestFocusFromTouch() solves this problem.
-justin
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Any solution to this?
On Jan 12, 4:23 am, Petroleum Nasby pnasby1...@gmail.com wrote:
I am struggling trying to have the soft keyboard appear in a search screen,
and from the looks of numerous pleas on various forums, I am not the only
one. I have tried many variants, culling from the
Hi Eric,
i dont have reply to this problem but i too am facing same
scenario .please if you can throw some light on to my problem i would
really appreciate that .
actually i am creating a custom view extending a textview, and then
trying to hook to the system softkeyboard throw the snippet you
I was wondering if anyone had access to one of the offending Hero
phones that has been updated via the OTA 1.6 roll out? Has the long-
press menu been addressed?
Best Regards,
Eric
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
On the HTC Hero, long-pressing-menu brings up an app switcher with
the last six apps. This works in almost all applications and provides
an alternative way to multi-task which is always available and quite
convenient.
Fragmentation, indeed! Ordinary HTC users would probably consider
other
On HTC Hero, long-pressing-menu has a completely different default
behavior: it brings up an app switcher with the last six apps. This is
available in almost all applications and makes multitasking very
convenient.
I develop on a Hero now and have to remind myself this is a non-
standard HTC
That's very interesting. Its the first I've heard of a feature being
tied to the long-press menu on a Hero. I don't have so I can't test
it, but no one else had mentioned that it had an alternate behavior -
just that it didn't bring up the keyboard. Is it possible that this
feature is the result
Jonas, that Hero app switcher comes not from long pressing the menu key, but
from long pressing the *Home* key. Long pressing the Menu key does nothing,
as others have noted.
2009/9/29 Jonas Beckman jonas.beck...@gmail.com
On HTC Hero, long-pressing-menu has a completely different default
As an update to the the code I showed above, I'm currently working
with the following code. This seems to be behaving the way I would
want it to.
On a phone with a physical keyboard:
- if keyboard is not hidden don't bring up the soft keyboard.
- if the keyboard is hidden, need to do the
In my situation, where I've used a series of custom views that don't
force the soft keyboard to display, I'm playing with the following to
allow the user to bring it up.
View.OnLongClickListener mLongClickListener = new
View.OnLongClickListener() {
@Override
The problem with long-pressing-menu not working is this: HTC Hero. It just
does NOT work there with the default keyboard.
I got also reports about people being not able to open the virtual keyboard
on their phones - I suggested them to try long-clicking the menu (following
Romain Guys suggestions)
On Fri, Sep 25, 2009 at 1:18 AM, tauntz tau...@gmail.com wrote:
The problem with long-pressing-menu not working is this: HTC Hero. It just
does NOT work there with the default keyboard.
Then they changed/broke something. (Which of those it is probably depends
on whether it is their IME doing
At any rate, long press on menu has ALWAYS been there purely as a very last
resort for pre-1.5 apps that couldn't have been written knowing about input
methods. It is a super-sucky mechanism to get to the soft keyboard, and
anyone writing an app today really should assume it doesn't exist
On the Hero and I guess other Androids as well, there is the Search
hardware button. This works in Hero Contacts AND in Launcher, bringing up
the soft keyboard. Not particulary intuitive I grant you, as you tend to
look for a button to do that on screen, but it does make sense.
Of course, in
On Fri, Sep 25, 2009 at 1:13 PM, James Webster jpbwebs...@gmail.com wrote:
On the Hero and I guess other Androids as well, there is the Search
hardware button. This works in Hero Contacts AND in Launcher, bringing up
the soft keyboard. Not particulary intuitive I grant you, as you tend to
Tauno and everyone else, thank you for your responses here.
Tauno, I have to agree with you that while long-press menu is not
intuitively obvious, it appears to be a standard means of bringing up
the soft keyboard (when it works) and said standard should be
maintained.
After all, it would seem
Dianne Hackborn wrote:
Long press on menu is NOT what you should be making your users do.
Seriously. It sucks. Who would guess that is how you get to a keyboard?
Please give them a decent UI.
Depends on the application. I just heard from one Hero user they are
unable to enter data in a
Perhaps my previous question was not clear, so let me see if I can
boil it down to something simple.
Given:
- an Android device running 1.5
- No physical keyboard
Question:
- How does the user force the soft keyboard to display?
- Does long-press menu do this?
- What other conditions have to
On Sep 24, 1:03 pm, Eric Carman ewcarma...@gmail.com wrote:
Question:
- How does the user force the soft keyboard to display?
- Does long-press menu do this?
Usually, however some means of catching key events will break this.
I agree with you that not having an emulator which behaves the
Long press menu forces the keyboard to be displayed, as long as the app
doesn't completely consume that key event, and there is a keyboard selected
and it allows this (the default behavior is to allow it).
On Thu, Sep 24, 2009 at 10:03 AM, Eric Carman ewcarma...@gmail.com wrote:
Perhaps my
Thank you both for your response.
If the application is written for Android 1.1, does this change
anything in regards to and there is a keyboard selected and it allows
this? I would think that in such an app, since it doesn't know about
soft keyboards, the system soft keyboard would be selected
On Sep 12, 11:08 am, Dianne Hackborn hack...@android.com wrote:
No, it is generally up to the IME to decide what it needs to do; you
certainly can't guarantee that it won't go fullscreen, because it just may
need to do so it have enough space to interact with the user.
One thing you will
On Sep 11, 9:52 am, Dianne Hackborn hack...@android.com wrote:
When in landscape, you aren't seeing -any- of your application, the IME is
running in fullscreen mode and completely covering it (so there is no reason
to do more work and resize the app to... nothing).
There is a flag (forgot
No, it is generally up to the IME to decide what it needs to do; you
certainly can't guarantee that it won't go fullscreen, because it just may
need to do so it have enough space to interact with the user.
One thing you will want to do is use flagNoExtractUi to tell it that full
extract mode is
There's a post on this groups regarding the resize issue. It seems that
using the FULL_SCREEN flag actually (as it's name suggests) makes the IME
unable to steal a part of the screen for display purposes.
And regarding the other problem... try using InputType.TYPE_NULL +
When in landscape, you aren't seeing -any- of your application, the IME is
running in fullscreen mode and completely covering it (so there is no reason
to do more work and resize the app to... nothing).
On Fri, Sep 11, 2009 at 8:27 AM, Howard M. Harte hhar...@gmail.com wrote:
When Android is
Only if you write your own IME.
On Tue, Jul 14, 2009 at 4:37 AM, I_Shove thomas.j...@gmail.com wrote:
Hello
Is it possible to change the layout of the softkeyboard ?
Regards
--
Dianne Hackborn
Android framework engineer
hack...@android.com
Note: please don't send private questions
For the second, it's because your view hierarchy is too deep, and doesn't
really have anything to do with the IME.
On Tue, Apr 28, 2009 at 4:53 PM, Rmac ry...@mac.com wrote:
I have views in my application that contain TextView components. When
clicking them to enter text I will get either
Hi, please don't post the same question multiple times.
The emulator does emulate a hard keyboard, so the behavior is correct. If
there isn't a hard keyboard the soft keyboard will be shown.
On Thu, Mar 5, 2009 at 8:14 AM, Julie j5ma...@gmail.com wrote:
Building from the source and using the
65 matches
Mail list logo
