meadl-devel team mailing list archive

[Jorge Silva <jsilva.idi@xxxxxxxxx>]

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
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