On Tue, Jul 5, 2011 at 1:57 PM, Isliguezze <[email protected]> wrote: > You can use this project created in Eclipse (simple demonstration) to > see the problem. Try to run it on emulator or on a device with D-Pad/ > Trackball. > > http://isvis.org/TestTabs.zip
For those of you just tuning in, this is in reference to: http://groups.google.com/group/android-developers/browse_thread/thread/23fcbaba2cd11ac8/6611fc481895bc82 To the OP: I would agree that the D-pad behavior is a bit odd. Since the behavior in this case is not documented AFAIK, whether it is truly a "bug" or merely unexpected behavior is up for debate. AFAIK there is no "fix" for this -- it is what it is. If I were a betting man, the core Android team did not put a ton of time into testing all possible D-pad scenarios as time went along, given that Android was focused on touchscreens. Now, as Google TV gets closer to supporting Android apps, there is probably more testing going on. This particular scenario might not be addressed, since Honeycomb tabs won't tend to use TabHost. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.6 Available! -- 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
