Kostya I think your right, even though the managedCursor mechanism basically does what I want I don't like it. I think the mechanism you mention in the destroy method is the way to go with this however I really think the platform should be looking after all of this correctly.
As you say all these things add up. For instance I would have thought a mechanism to associate an autocomplete field with a database query would have been built into the platform and I would just need to setup some simple hooks and the platform would deal with everything. As it is I feel like I am trying to jump through hoops and all the time not working on the real business logic of my app. -- 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
