It sounds strange because it's not how inheritance should work. Baseclass should only implement the common/default behavior. Whatever the 'what' variable is used, it should be accomplished by having A and B implementing/overriding operations defined on the BaseClass. About the issue, you might get better conclusions by putting logs or breakpoints on the lifecycle methods on all three activities and observing the intent's componentname on the calls
On Sep 26, 10:59 pm, SpaceJack <[email protected]> wrote: > > That sounds terrible =) > > > Anyway ... you're sure the life cycle methods in the base class are > > definitely being called for A and B the way you think they are? That is, > > when you see onRestart, for example, you're sure that's for B and not for A? > > > And there's nothing with statics? > > > Not sure what else to tell you. Sounds like it should work ... > > Thanks for your help. Unfortunately, currently I have no time to fix > that issue. Nevertheless the problem stays and maybe later I'll return > to it. BTW why it's terrible? :) -- 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
