I'm glad that you've found a solution that works for you. Yes,
unfortunately while we expect most Android devices to be pretty
powerful and have fairly large amounts of memory, they still aren't
desktop machines and more careful design and implementation will
sometimes be necessary.
Cheers,
Mark,
Great book. I recommend it to all.
I like the subscription model also. Very cool.
Bob
On Dec 10, 7:57 am, Justin (Google Employee) [EMAIL PROTECTED]
wrote:
I'm glad that you've found a solution that works for you. Yes,
unfortunately while we expect most Android devices to be pretty
BobW wrote:
Mark,
Great book. I recommend it to all.
I like the subscription model also. Very cool.
Thanks!
--
Mark Murphy (a Commons Guy)
http://commonsware.com
_The Busy Coder's Guide to Android Development_ Version 1.9 Available!
--~--~-~--~~~---~--~~
Once upon a time I spent a lot of time debugging this issue, so here
is what I found.
***WARNING: This information was valid on an internal version of the
SDK between M5-RC15 and 0.9 beta, it may no longer be valid, test
thoroughly and proceed with caution.***
First, some information about
Okay this kind of makes sense, so to ensure the map is always showing
the correct view (i.e. city), one should reposition the map each time
the activity is loaded?
One question though, what happens if someone clicks the back button?
Does the original activity reload automatically, or do you have
... Just to add to my question above ...
If only one MapActivity is allowed per process - I take it that
means per application??? - How does one properly use 2 or more maps
per application?
On Dec 8, 12:17 pm, mscwd01 [EMAIL PROTECTED] wrote:
Okay this kind of makes sense, so to ensure the map
mscwd01 wrote:
If only one MapActivity is allowed per process - I take it that
means per application???
By default, yes, though it does not have to be that way:
http://code.google.com/android/intro/appmodel.html
How does one properly use 2 or more maps
per application?
If the quoted bit
I've had a look at the documentation you suggested, however I think im
misunderstanding how you launch a new activity in a seperate process.
Is there a demo which illustrates this?
On Dec 8, 12:36 pm, Mark Murphy [EMAIL PROTECTED] wrote:
mscwd01 wrote:
If only one MapActivity is allowed per
mscwd01 wrote:
I've had a look at the documentation you suggested, however I think im
misunderstanding how you launch a new activity in a seperate process.
Is there a demo which illustrates this?
U...none I'm aware of. The ApiDemos in the SDK show separate
processes, but for services,
Okay, one last question ;)
I've noticed if I have one map in, say, Activity1 and I call another
activity, Activity2 which has a map within a tab of a TabHost - If I
press the back button and go from Activity2 to Activity1, the map in
Activity1 doesn't update i.e. load new tiles - only the map in
Oh btw I purchased your The Busy Coder's Guide to Android
Development book - its very helpful ;)
On Dec 8, 11:30 pm, mscwd01 [EMAIL PROTECTED] wrote:
Okay, one last question ;)
I've noticed if I have one map in, say, Activity1 and I call another
activity, Activity2 which has a map within a
mscwd01 wrote:
Hope I havent confused you ;)
No, but you have made my head hurt.
Oh btw I purchased your The Busy Coder's Guide to Android
Development book - its very helpful ;)
My head feels better now... ;-)
However what i'm asking is, is there a way to kill off Activity2
completely
Okay, I think its just a case of not having enough memory, so for now
I'll forget switching between two activities where one activity
launches a new MapActivity instance.
I have created another version of my app which uses one MapView,
however that too has some problems ;)
Fancy having a look
Having tried the test you suggested it seems I can go back and forth
between my Activity1 map and the inbuilt Google Maps app perfectly
fine - no memory worries. However my application, constantly throws up
OutOfMemory errors.
One thing I have noticed is after Activity1 calls Activity2,
Anyone? I cant work out what is causing this...
On Dec 7, 5:16 pm, mscwd01 [EMAIL PROTECTED] wrote:
I have a weird issue, which is probably easily solvable - but the
cause is alluding me.
I have two activities, one is created as an intent from the first
activity. Each activity features a
Sounds like your maps share some common underlying resource. Not sure
if that would be a defect or by design. Perhaps you can manually call
onSaveInstanceState() and onRestoreInstanceState() to save / restore
the respective maps state as needed?
I have two xml layout files, one for each activity, I create the maps
like:
MapView myMap = (MapView) findViewById(R.id.map);
and...
MapView myMap = (MapView) findViewById(R.id.mapTwo);
Yet, even though they have different id's they control each other...
I shouldnt need to save the state of
I have a weird issue, which is probably easily solvable - but the
cause is alluding me.
I have two activities, one is created as an intent from the first
activity. Each activity features a MapView.
Only one MapActivity is supported per process. Multiple MapActivities
running
This Has Already Been Posted.
On 12/07/2008, Tom Gibara [EMAIL PROTECTED] wrote:
I have a weird issue, which is probably easily solvable - but the
cause is alluding me.
I have two activities, one is created as an intent from the first
activity. Each activity features a MapView.
Only
19 matches
Mail list logo
