So, ive seen that the view inside that tab has focus. So it cant be a
focus problem. Its a strange behaviour bcos an edittext get the focus,
but its not orange-highlighted. I press down and up in the pad and
that edittext gets highlighted. If i press menu button after that,
then i can see the menu
Ok, understood. But i can't change now the way i manage those tabs. I
will consider your solution in future apps.
I think that the main reason to use Intents instead of views is that
some views can be hard to manage and the final TabActivity can be
really heavy to load and really ugly to read (the
khose wrote:
> Any idea??
Frankly, I have yet to see a good reason to use Intents to populate
tabs, particularly since you are limited to your own activities.
If this were my code, I would:
1. Move the UI logic for each of the activities to be put into tabs into
custom View classes rather than
Any idea?? I've seen that everythig goes right when you define your
layout inside the tab container XML and you manage all the tabs within
the TabActivity. But its really confusing when you throw intents
instead. I also have some issues with the menu that each tab is
showing up
On 21 abr, 20:
4 matches
Mail list logo
