You MUST submit a patch to the open source project to have the new events added to the platform, and we'll work with how that should either be expressed as a more generic code, or just accept that as a specific one. We really want to avoid having the same kind of key event defined with different values by different vendors.
On Thu, Apr 9, 2009 at 9:25 AM, jrukman <[email protected]> wrote: > > Is there a model to extend the set of keycodes available in the > Keyevent.java keycodes for new devices so that applications can access > and use these keys? > > I have a device that has several external softkeys for additional > actions that do not fit into the existing keycode set. Just adding > these to the keyevent keycodes seems like a recipe for trouble for > application developers if this isn't coordinated somehow. > > Is there some other concept that I'm missing to do this? eg. I see > KEYCODE_UNKNOWN here that might perhaps be leveraged to support device > specific hard keys? > > thanks, > Jason. > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
