On Sat, Oct 1, 2011 at 8:42 AM, Dianne Hackborn <[email protected]> wrote:
> What do you mean by go to settings and map their buttons? There is a > well-defined keycode for search; you shouldn't need to ask the user to map > that to anything. Sure, but as I mentioned in a previous message I'm explicitly and intentionally *not* using the button to search. I'm working on a game (well, entertainment software would be a more precise description but anyway ...) and to make it short, I'm just looking for a convenient way to control the program during development. Note this is *not* meant for release controls, at least at the moment. The problem is developers need to access more internal functionality directly (e.g. for testing) than will be exposed to the end user so I'm just looking for something reasonable to bind this to. In this case, it's much more convenient to operate the program using off-screen controls so I'm looking to leverage whatever the devices has. I already have a section in Preferences that lets people pick a control scheme based on what their device has so that's not a problem. I just thought if I could detect it myself I could automatically select a good default for the user. If I can't check I have to set the default to the least convenient scheme that works everywhere and ask everybody with devices that support more to set their controls manually. What would be the problem with letting programmers check if there's something on the device that sends KEYCODE_SEARCH? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
