Hi, I suggest not relying on devices having Trackabll / D-pad, many don't.
Regards On Oct 27, 10:53 pm, andfan22 <[email protected]> wrote: > Hi all > > When creating a tabbed display using TabHost & TabWidget, one of the > options for specifying the tab content is > TabHost.TabSpec.setContent(Intent intent), which causes an activity to > be launched as the tab content. This works fine except for one > problem. I can't seem to use the trackball / d-pad to change focus > from a field within the tab content (running as an embedded activity) > to a field in the parent activity that is positioned below the tab > content. The trackball / d-pad can be used to navigate to a field > ABOVE the tab content, but not below. > > This problem disappears if the tab content is specified using > TabHost.TabSpec.setContent(int viewId) instead of setContent(Intent > intent). > > Does anyone know how to fix the above navigation issue for tabs that > use embedded activities? > > Thanks in advance ... -- 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
