Thanks but isn't that more for across processes rather than across
activities within a process?
On May 9, 7:17 am, Senthil ACS acs@gmail.com wrote:
I remember there is an interface named CrossProcessCursor that
implements Cursor.
Specify this interface in your aidl interface method.
On
Check your logic, sharing a cursor between 2 activities is really necessary?
2010/5/9 westmeadboy westmead...@yahoo.co.uk
Thanks but isn't that more for across processes rather than across
activities within a process?
On May 9, 7:17 am, Senthil ACS acs@gmail.com wrote:
I remember there
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!
On May 9, 12:13 pm, Second Dancer
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
Interesting. So, essentially, anything that cannot be passed in the
Intent could be passed via a local service. Is this a common tactic in
general?
What are the main advantages over just setting the objects as statics
on the secondary activity?
One, is the situation where the activity is killed
westmeadboy wrote:
Interesting. So, essentially, anything that cannot be passed in the
Intent could be passed via a local service. Is this a common tactic in
general?
I can't say whether or not it's common. It's certainly something I
recommend here and there.
What are the main advantages
On May 9, 12:52 pm, Mark Murphy mmur...@commonsware.com wrote:
Actually, that's one of the minuses, IMHO.
A static data member survives the rotation. The service, however, will
shut down mid-rotation if there are no other bound connections to it.
Right now, you have to manage the orientation
westmeadboy wrote:
I remember using statics before and then (through analytics) finding
that those statics were sometimes null unexpectedly. I came to the
conclusion that this was something to do with the system killing
processes and automatically restarting them (and whatever activity)
I just stick android:configChanges=keyboardHidden|orientation in my
manifest. I generally do that by default these days. Haven't come
across any problems so far!
Does that explain why it works?
On May 9, 1:13 pm, Mark Murphy mmur...@commonsware.com wrote:
westmeadboy wrote:
I remember using
westmeadboy wrote:
I just stick android:configChanges=keyboardHidden|orientation in my
manifest. I generally do that by default these days. Haven't come
across any problems so far!
Does that explain why it works?
Yes, as that will disable the automatic destroy-create cycle for the
activity.
Any strong reasons to not take that manifest approach?
On May 9, 1:28 pm, Mark Murphy mmur...@commonsware.com wrote:
westmeadboy wrote:
I just stick android:configChanges=keyboardHidden|orientation in my
manifest. I generally do that by default these days. Haven't come
across any problems
westmeadboy wrote:
Any strong reasons to not take that manifest approach?
So long as your UI is rendering the way you want in both orientations, I
am not aware of any problems.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog |
I remember there is an interface named CrossProcessCursor that
implements Cursor.
Specify this interface in your aidl interface method.
On May 8, 7:21 pm, westmeadboy westmead...@yahoo.co.uk wrote:
In one activity I build a cursor which is used to populate a ListView.
I want a secondary
13 matches
Mail list logo
