Hi,
As Zach Hobbs wrote on month ago, a solution is to launch either the
widget or the configure activity (and all sub-activities containing
the MapActivity) in an another process than the application by
specifying in the AndroidManifest.xml file the option
"android:process" as following:
For example below, we launch the widget in the private (because of the
':') process "otherPrivateProcess":
<application ...>
<receiver android:name=".myWidget"
android:process=":otherPrivateProcess" ...>
...
</receiver>
...
</application>
Seb.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
