Skip to Content
author's profile photo
Former Member

PDA Keyboard Mapping Problem

Hi All,

I am involved in a project in which my coding revolves around MI AWT client application part. I had no problem in extraction of data from MI middle ware, thanks to MI sync APIs and this forum.

My problem is more of Java centric and will like to pose questions to those developers who may have encountered similiar problems.

I am testing MI AWT application on emulator using Intermec 700c skin as well as on Desktop. Our client wants to enable keyboard handling also so that user will be able to execute operations on application without much use of stylus. I have applied keyListener to all the components of my application including HomeFrame's instance. But still my keyboard handling is working sometimes and sometimes it's not working. This is due to fact that application is losing focus on certain occasions which I am unable to track. But even if application is losing focus,according to my understanding, focus must be at least on HomeFrame and any of it's child component. I have added keyListener to HomeFrame and all of its child components also.

Have anybody encountered similiar problem? Can anyone help me in this regard? This keyboard thing is an important aspect of client side application, which I am finding difficult to solve.

Thanks and Regards,


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    author's profile photo
    Former Member
    Posted on Sep 27, 2007 at 04:55 PM

    hi gopa,

    when the window lost it's focus, then the key events won't be directed to your

    application window since the active app is different. you can implement a

    windowlistener and you app will be notified once your window gets deactivated i.e.

    some other app gets activated. what you observed is a normal behavior.

    hope this help


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Jo,

      Thanks for the response.

      By implementation of AWTEventListener (Not available in Java 1.1.8, just implemented for debug basis), I found out that, if focus is on any hidden component, key events on such component will not work. That is what was happening with our application. I was able to solve this problem after this discovery. But still problem remains in one account which now we have to put in bugs of our application.

      On MI home page, when user clicks on button to execute our application, our application opens up but still focus remains with that button on MI home page due to which key event is not firing for first time as that button now becomes hidden. I tried request focus for our application's first screen's panel when that panel is shown but still it's not working. So still problem persists only on this account. Now we will ship our application with this bug. No other go.

      Hope I have not complicated the explanation....:-)