westmeadboy wrote: > I really cannot think of any other way to do it, short of copying the > contents of the cursor into some other object. > > Requerying the database is not an option because these are not simple > SQLiteCursor instances. > > Please feel free to suggest alternatives!
Have the data be managed by a local service. Have the activities bind to the local service. Have the activities request a cursor via methods on the local service when they need it. Pass truly transient data (e.g., the position of the row the 2nd activity should look at) as Intent extras. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Consulting: http://commonsware.com/consulting -- 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
