And you already have the answer to that question, even several times now: the answer is no, it is not feasible, not under the constraints you have imposed on yourself. You need to redesign. This time, take into account that the process is an anonymous container.
BTW: am I really the only one to notice, big though your application may be, that it has "hundreds of Activities" sounds like another symptom of fundamentally flawed design. Have you considered the Flyweight design pattern? I know that would entail a massive rewrite at this point, but it sounds to me like you have painted yourself into a corner as things are, so it may be time for it. On Jul 25, 8:55 am, elDoudou <[email protected]> wrote: > Thank you Mark. > > However, you still do not answer my question, and this coding design > pattern does not help in that specific situation. I do not need a work- > around, I'd like to know if what I attempt to achieve is feasible. > > Thank you for your understanding. > Édouard -- 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
