I hope that I'm wrong, but here's my understanding... Let's say my 2 app manifests contain something like this:
<application package="my.package"/> <activity name=".MyActivity"/> <application package="my.packagepro"/> <activity name=".MyActivity"/> Rather than maintaining 2 copies of MyActivity, I move them into a library: <application package="my.package.core"/> <activity name=".MyActivity"/> Now the references in my apps need to be updated: <application package="my.package"/> <activity name="my.package.core.MyActivity"/> <application package="my.packagepro"/> <activity name="my.package.core.MyActivity"/> Here's where the problem started. Any existing appwidgets on the homescreen would disappear. Then I found this: http://android-developers.blogspot.com/2011/06/things-that-cannot-change.html So, I've reverted my manifest's back to a local package reference: <application package="my.package"/> <activity name=".MyActivity"/> <application package="my.packagepro"/> <activity name=".MyActivity"/> ...however, that class isn't in my.package or my.packagepro, it's in the library, my.package.core, so my understanding is that I needed a local version of the class. Am I wrong? Can I leave the activity name as ".MyActivity" and it will reference my.package.core.MyActivity? I though that when the name begins with a ".", then the application package is used. Thank you! Bryan -- 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
