Okay, as I could not find a way to fix that smoothly, I just used a flag
ignoreNextOnItemSelected like described hereafter. Seems to me a dirty hack
:(
// called from another activity context
updateSpinnerSelection(int newposition) {
mPosition = newposition; // store it
Thierry,
I think you are seeing interaction between the activity's
onRestoreInstanceState and your setSelection.
Should be pretty easy to check by overriding onRestoreInstanceState in
ActivityA and/or the spinner and logging them - as well as your code
that calls setSelection. Then you can
Hi Kostya,
Thanks to try to help to sort this out. unfortunatly I don't think this is
the cause in this case:
Activity A is a TabActivity that embeds activity B being in tab 2. Indeed
when I select tab 1 from activity B using setCurrentTabByTag , *Activity A
is already in running state* (I
(putting again CC to android as your answer seems quite usefull to android
community!)
Wow, thanks Kostya, I am impressed by this so detailed answer :). Answers
inline.
2011/3/2 Kostya Vasilyev kmans...@gmail.com
Yes, if the activity isn't getting recreated, there won't be
02.03.2011 16:23, Thierry Legras пишет:
(putting again CC to android as your answer seems quite usefull to
android community!)
Thank you. I meant to reply to the list, but Thunderbird sometimes has
other ideas :) And good luck to you with resolving the issue.
Wow, thanks Kostya, I am
5 matches
Mail list logo
