Hello,
I think i myself found the solution.
using android:windowSoftInputMode="stateAlwaysHidden|adjustResize" fixes the
issue.
adjustPan was also one alternative but its not behaving consistently. Also i
read the below post from Dianne Hackborn regarding adjustPan:-
*
I should describe what my complete scenario is. I have several
Fragments in my Activity, all but one of which are hidden at any given
time. When a Fragment with an EditText is getting hidden, I want to
ideally keep the virtual keyboard if the next Fragment being unhidden
also has an EditText. The v
Thanks Federico,
I've tried using ListView within Scrollview but unfortunately ScrollView
does not work with ListView! :(
On Fri, Dec 31, 2010 at 7:50 PM, Federico Paolinelli wrote:
> Having your view wrapped into a scroll view should make the trick.
>
> http://schemas.android.com/apk/res/andro
Having your view wrapped into a scroll view should make the trick.
http://schemas.android.com/apk/res/android";
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:fillViewport="true">
To be honest, I never tried it with a listview, but it worked quite
wel
Hello
Take a look at this thread:
http://groups.google.com/group/android-developers/browse_thread/thread/9d1681a01f05e782
As Dianne says, the only way is to implement onSizeChanged() for your
View.
On Sep 27, 5:58 am, Shoyeb Irfan wrote:
> How can I get an event when the user opens or closes th
I had this same problem a couple weeks back. I'm not addressing any
of the remaining discussion in this thread regarding Activity
constructors, resetting of content, etc..
But i did have input(type=text) and textareas that I simply could not
focus on via touch..As a Dev i readily ignored it, usin
Dan,
please add the line in OnFocusChange() or setOnEditorAction() listener
of your EditText view.
added there, it works for me.
On Apr 7, 11:08 am, d...@rolph.com wrote:
> HeHe,
> I added that line to my activity, and I still get the virtual keyboard after
> the return key is pressed. Pressi
HeHe,I added that line to my activity, and I still get the virtual keyboard after the return key is pressed. Pressing the return key only adds a new line to my EditText. Did I implement it improperly? Here is a sample piece of code testing the functionality:public class Login extends Activity {
//the keyboard now
((InputMethodManager)getSystemService(Context.INPUT_METHOD_SERVICE)).hideSoftInputFromWindow(v.getWindowToken(),
0);
On Apr 7, 10:09 am, d...@rolph.com wrote:
> Hello,
> Is there a way to configure the virtual keyboard to "hide" once the return
> key is pressed? I have numero
Hi Nithin,
Thanks for your replay..
Thanks
C.Rajesh
On Apr 5, 11:56 am, Nithin wrote:
> This is the default behaviour of Android. If user click on the
> EditText, virtual keyboard will appear..
>
> Nithin
>
> On Apr 5, 11:52 am, rajesh chandrasekaran
> wrote:
>
> > Hi All,
>
> > I am new in
Hi Kumar Bibek,
Thanks for your replay..
how to focus the editText
Thanks
C.Rajesh
On Apr 5, 12:47 pm, Kumar Bibek wrote:
> This is a default behaviour in Portrait mode only when there is a
> hardware keyboard.
>
> If there is no physical keyboard, then the on screen keyboard should
> sh
This is a default behaviour in Portrait mode only when there is a
hardware keyboard.
If there is no physical keyboard, then the on screen keyboard should
show up in both orientations. This is a default behaviour and you
don't need to do anything special for it.
Make sure that you are using the Ed
This is the default behaviour of Android. If user click on the
EditText, virtual keyboard will appear..
Nithin
On Apr 5, 11:52 am, rajesh chandrasekaran
wrote:
> Hi All,
>
> I am new in android, i am having problem in Virtual Keyboard.
>
> I am having text field. if user click the text field th
To tackle the flip side of what Mark is saying, just to give you
another way to get it: 'new XX()' is NOT implementing a constructor --
it is calling one, but it does not implement one.'
Mark missed a point though -- a constructor without a call to super()
will always call the default super().
Yo
On 03/17/2010 04:17 PM, Mark Murphy wrote:
mike wrote:
Oh! You should take that up with Google then because that's their
HelloActivity example code. I didn't change a thing there. If it
causes trouble, it's probably endemic because Hello World is where
most beginners start.
Seriously?
mike wrote:
> Oh! You should take that up with Google then because that's their
> HelloActivity example code. I didn't change a thing there. If it
> causes trouble, it's probably endemic because Hello World is where
> most beginners start.
Seriously?
I don't see a "Hello Activity" example on thei
On 03/17/2010 03:46 PM, Mark Murphy wrote:
mike wrote:
We're not communicating. Are you saying that the only time
I should do a new XX() is *only* in onCreate?
No, we're definitely not communicating.
As I wrote:
1. Never implement a constructor in an Activity.
In Java, "implement"
mike wrote:
> We're not communicating. Are you saying that the only time
> I should do a new XX() is *only* in onCreate?
No, we're definitely not communicating.
As I wrote:
1. Never implement a constructor in an Activity.
In Java, "implement" means "to write code".
Your sample code had:
publi
On 03/17/2010 03:04 PM, Mark Murphy wrote:
mike wrote:
We already proved that what you did here worked yesterday.
I don't want to setContentView to the webview initially. I want
to be able to paint up a screen and switch to the webview later,
via user control (ie, a button/menuitem).
mike wrote:
> We already proved that what you did here worked yesterday.
> I don't want to setContentView to the webview initially. I want
> to be able to paint up a screen and switch to the webview later,
> via user control (ie, a button/menuitem).
Then make the WebView have visibility of GONE at
We already proved that what you did here worked yesterday.
I don't want to setContentView to the webview initially. I want
to be able to paint up a screen and switch to the webview later,
via user control (ie, a button/menuitem).
1) I don't know what you mean by "never implement a constructor
mike wrote:
> Ok, here is a complete app that exhibits the problem. The key that is
> necessary is to
> do a setContentView from the menuItem/onClick/onLongClick. It doesn't
> help if you
> postpone it either, eg using handler.postDelayed() and such.
>
> This is a rather serious bug for anything t
Ok, here is a complete app that exhibits the problem. The key that is
necessary is to
do a setContentView from the menuItem/onClick/onLongClick. It doesn't
help if you
postpone it either, eg using handler.postDelayed() and such.
This is a rather serious bug for anything that uses a WebView.
Th
On 03/16/2010 08:12 AM, Mark Murphy wrote:
mike wrote:
Can somebody from google please comment?
In case you haven't noticed, the percentage of questions that get asked
here that get answered by Google is fairly small.
this seems like a pretty
serious error in the webview's if yo
mike wrote:
> Can somebody from google please comment?
In case you haven't noticed, the percentage of questions that get asked
here that get answered by Google is fairly small.
> this seems like a pretty
> serious error in the webview's if you can't type into a html input or
> textarea
> box on,
On 03/16/2010 12:22 AM, Farha Ansari wrote:
Yes, I had the same issue, and it has not been solved till now. I had
also posted the question but didnt get any reply.
I hope, someone would reply this time to your post.
Can somebody from google please comment? this seems like a pretty
serious e
Yes, I had the same issue, and it has not been solved till now. I had
also posted the question but didnt get any reply.
I hope, someone would reply this time to your post.
Farha
On Mar 16, 5:30 am, mike wrote:
> Hi all,
>
> I'm having a very very strange problem with input and textarea html
> ta
Figured this one out.
Launched the virtual keyboard and got the keys through
dispatchkeyevent.
Works fine!
Thanks,
Ashwini
On Aug 18, 9:31 am, Ashwini wrote:
> Hi,
>
> Is is possible to get the virtual keyboard key events on a custom
> input field ?
> I tried using keyboardView, but somehow tha
u cud use intents, based on the keypress call the appropriate intents and
the corresponding finish() for the activities.
On Sun, Jun 28, 2009 at 10:10 PM, ozzoozzo wrote:
>
> I have a virtual keyboard and EditText on the screen and want to do
> the following :
> 1) If the user hits Cancel, the
Virtual keyboards and other input methods will not be supported in the
system until a feature release:
http://source.android.com/roadmap
On Sun, Nov 23, 2008 at 12:55 PM, skink <[EMAIL PROTECTED]> wrote:
>
> hi,
>
> i created yavk (yet another virtual keyboard) -
> http://www.filefactory.com/fil
30 matches
Mail list logo
