meadl-devel team mailing list archive

[Rishabh Garg <rishabhgarg1992@xxxxxxxxx>]

Hi Jorge,

I think I have found the solution for triggering the options menu via a key
event. I have also tracked why something else was being triggered by the
options menu key-code, the problem which Kevin was facing on his device.
Here are my findings-


   -

   I started by changing the key-code value for one of the navigation
   key(the right key) to the key-code of the menu key(82) in the xml file. As
   Kevin mentioned earlier, this was triggering something weird instead of the
   menu
   -

   I then tried replacing the menu key-code by all other possible key-codes
   to check which of the key-codes behaved differently.
   -

   When experimenting with different key-codes resulted in nothing,I decided
   to backtrack the flow of code that resulted in the key-event.
   -

   I printed the key-code received by keyUpDown function in the log, to
   check if the correct event was received by the function.
   -

   After checking the log for various key-codes in xml, I found that the
   keyUpDown function received key-codes for some specific keys only, and this
   function was not called for rest of the cases.
   -

   I started to find the functions that called the keyUpDown function and
   analyze them.
   -

   I found that that keyUpDown function was called by a handler function for
   nav bar, which in turn was called by onKey function. For some reason the
   onKey function was not able to call the handler function for nav bar, and
   instead called some other function which generated some other event.
   -

   It finally turned out that the onKey function uses another function to
   check key-code it reveives, isNavigationKey function.
   -

   isNavigationKey function checks whether the recieved key code belonged to
   a set of key-codes(up,down,left,right,center or back). If it does, it passes
   it to KeyUpDown function via handler , but for any other key code, it passes
   it to handleCharacter function, which uses prediction etc. to trigger
   some other key-event. This is the reason some other event was triggered in
   Kevin's device.
   -

   I added the key-code for menu in the set of key-codes in the
   isNavigationKey function, which enabled it to pass the key-code for menu to
   keyUpDown function.
   -

   The KeyUpDown function was able to trigger the key-event for menu
   correctly .

I changed the key-code of* right button in nav bar* to act as *menu button*.

After checking the new code on emulator, I have also thoroughly checked it
on my device. The menu is correctly opened for android homescreen as well as
all 3rd party applications(Gmail,Gtalk,
Youtube etc.) by the right button in nav bar.

I have uploaded the new apk with these change on this link-
http://web.iiit.ac.in/~rishabh.garg/IMESettings.apk. Could you please
confirm if the above solution is working fine or if there is any problem in
it.

I would also update my findings on this wiki page -
http://wiki.scyp.atrc.utoronto.ca/w/Tekla/Accessible_Options_Menu.

.I think this solves the first 2 points of our solution blueprint-
1. Open the options menu programatically
2. Detect the event triggered when the options menu is open,


Regards
Rishabh Garg


On Thu, Apr 14, 2011 at 3:09 AM, Jorge Silva <jsilva.idi@xxxxxxxxx> wrote:

> Hola,
>
>  As many of you already know, Tekla users are still locked out the
> options menu because of two reasons:
> 1. When the menu pops-up, it occludes the keyboard, and
> 2. Even when the keyboard remains active, its key events are sent to the
> activity underneath, instead of to the menu on top
>
> The Google accessibility team has confirmed the issue is in the Android
> framework and they are working on it, but we'll try a workaround that
> has been drafted in the following blueprint:
> https://blueprints.launchpad.net/meadl/+spec/accessible-options-menu
>
> Long-story short, in order to make this happen, the first thing we need
> to do is make sure Tekla can open the options menu on any app,
> programatically. The Goldeneye
> (http://wiki.scyp.atrc.utoronto.ca/w/Goldeneye_Reading_Project) project
> devs already tried to do so by sending the corresponding key event but
> the device they tested on wasn't very cooperative. We need to do the
> following:
> 1. Confirm whether in fact it is not possible to send the key event
> using the current methods (code is at: http://goo.gl/dOenl)
> 2. If the key event doesn't work, try other methods like:
> http://stackoverflow.com/questions/3133318/open-the-options-menu-
> programatically or
> http://mylifewithandroid.blogspot.com/2009/01/generating-keypresses-
> programmatically.html<http://mylifewithandroid.blogspot.com/2009/01/generating-keypresses-%0Aprogrammatically.html>
> 3. If none of that works, then we should try looking for an intent
>
> Let me know if any of you would like to help trying this out... I am a
> bit tied at the moment with other commitments. If you have any other
> questions please feel free to reply to the thread.
>
> cheers!
> Jorge
> --
> This message was sent from Launchpad by
> Jorge Silva (https://launchpad.net/~jorge-silva)
> using the "Contact this team" link on the Tekla development team team page
> (https://launchpad.net/~meadl-devel).
> For more information see
> https://help.launchpad.net/YourAccount/ContactingPeople
>
> _______________________________________________
> Mailing list: https://launchpad.net/~meadl-devel
> Post to     : meadl-devel@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~meadl-devel
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Rishabh Garg
B.Tech CSE 2nd year
International Institute of Information Technology(IIIT)
Hyderabad,India