On Wed, Jun 8, 2011 at 7:55 PM, Duskox <dus...@gmail.com> wrote: > Ok, I have an idea. Since I have a myXMLHandler object I will create a > public function in it that will fill a temporary ArrayList and return > it to me through this function. Then I will just put it in my > Application object. Only thing is that this way I can not use the > object I defined in myApp class...unless I pass my Application object > to myXMLHandler first :) > > Ok that solves it I guess but if there is a better way to do this data > passing please do write.
Well, it's impossible to tell you "if there is a better way to do this data passing". Most likely, there is. However, it is completely unclear what you are "passing" data between. I was merely pointing out that an Application object is not a significant improvement over static data members, at the cost of being more difficult to access. You still have all the standard memory leak issues, whether the data is held in an Application or in static data members, for example. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 3.0 Programming Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
