okay thanks Dianne. You have been great help!
One more question(sorry to keep troubling you): Is there any way to
have my OWN softkeyboard just for one application.
Eg: I have an EditText. I want a custom softkeyboard to show only when
I edit this text box only in my app. I dont want it to be
I want to implement a biometric measure based on keystroke analysis.
(This is a known research topic).
I need to extract timing vectors that correspond to how a user types.
(This is done on other devices like Win Mob but not Android)
Suppose a user types EARLENCE (length of string = 8)
It should
You can use they keyboard class to implement your own IME inside of the app.
You can't do this with the IME framework, since that is global.
On Sat, Sep 4, 2010 at 9:10 PM, Tez earlencefe...@gmail.com wrote:
I want to implement a biometric measure based on keystroke analysis.
(This is a known
Thanks Dianne. I have implemented my own keyboard with the keyboard
view class.
Cheers,
Earlence
On Sep 5, 9:10 am, Tez earlencefe...@gmail.com wrote:
I want to implement a biometric measure based on keystroke analysis.
(This is a known research topic).
I need to extract timing vectors that
On Mon, Sep 6, 2010 at 12:37 AM, Tez earlencefe...@gmail.com wrote:
So the KeyEvent Listener is only for physical keyboards?
I see many devices that have only soft keyboards. This leads me to
think What is the value of the Key Listener API then?
It predated the IME system. Hence, if nothing
In all these key interactions, (physical or
IME), am I correct in assuming that all data must pass thru the
Framework classes like WindowManagerService, KeyInputQueue etc?
-E
On Sep 6, 2:18 pm, Mark Murphy mmur...@commonsware.com wrote:
On Mon, Sep 6, 2010 at 12:37 AM, Tez
KeyListener is (generally) only for physical keyboards. It may not even be
used for those -- an IME has first crack at hard key events and may do its
own massaging of them and do calls on its InputConnection. (Consider for
example a Chinese IME that converts input on a hard keyboard to Chinese
Thank you for the quick reply.
So now, coming back to my original problem, is there ANY way that you
can think of to receive the information I need
without writing a custom IME?
Cheers,
Earlence
On Sep 7, 8:42 am, Dianne Hackborn hack...@android.com wrote:
KeyListener is (generally) only for
I have been try to say -- no. The information you are asking for doesn't
even exist. There are no key events.
On Mon, Sep 6, 2010 at 8:52 PM, Tez earlencefe...@gmail.com wrote:
Thank you for the quick reply.
So now, coming back to my original problem, is there ANY way that you
can think of
No, what I mean is that is there any other *similar* measure that is
obtainable from the framework,
or what the framework provides?
-E
On Sep 7, 9:08 am, Dianne Hackborn hack...@android.com wrote:
I have been try to say -- no. The information you are asking for doesn't
even exist. There are
I mean to say that is there any other measurable parameter the IM
framework provides?
On Sep 7, 9:08 am, Dianne Hackborn hack...@android.com wrote:
I have been try to say -- no. The information you are asking for doesn't
even exist. There are no key events.
On Mon, Sep 6, 2010 at 8:52 PM,
I've told you what there is.
On Mon, Sep 6, 2010 at 9:25 PM, Tez earlencefe...@gmail.com wrote:
I mean to say that is there any other measurable parameter the IM
framework provides?
On Sep 7, 9:08 am, Dianne Hackborn hack...@android.com wrote:
I have been try to say -- no. The information
Biometric Measure with neural nets: Key stroke patterns.
For that I need data about how something was typed in:
Eg: EARLENCE
1. time for which each key was pressed.
2. interval between consecutive key presses.
Cheers,
Earlence
On Sep 4, 10:44 pm, Dianne Hackborn hack...@android.com wrote:
You
You can't get that from the IME. What you get is edit operations via calls
on InputConnection.
You will need to implement your own keyboard in your app if you want to
monitor individual interactions with it.
On Sun, Sep 5, 2010 at 4:18 AM, Tez earlencefe...@gmail.com wrote:
Biometric Measure
So the KeyEvent Listener is only for physical keyboards?
I see many devices that have only soft keyboards. This leads me to
think What is the value of the Key Listener API then?
Cheers,
Earlence
On Sep 6, 12:02 am, Dianne Hackborn hack...@android.com wrote:
You can't get that from the IME.
and another thingin all these key interactions, (physical or
IME), am I correct in assuming that all data must pass thru the
Framework classes like WindowManagerService, KeyInputQueue etc?
Cheers,
Earlence
On Sep 6, 12:02 am, Dianne Hackborn hack...@android.com wrote:
You can't get that
How do I intercept the InputConnection Calls? Would I have to modify
the IME or use a custom one?
Having text change listeners would not be of use as I need key timing
information. This I can only get thru KeyEvents.
Cheers,
Earlence
On Sep 4, 12:39 pm, Dianne Hackborn hack...@android.com wrote:
You can override EditText to return your own InputConnection.
But... if you want KeyEvents, you won't get KeyEvents. Period. There are
no KeyEvent objects involved in this ANYWHERE. At all. The user is
touching on the screen (that is a touch event). The IME turns that into an
edit operation
18 matches
Mail list logo
