On Thu, Jun 14, 2012 at 8:48 AM, Bryan <[email protected]> wrote: > It seems like I'm on the right track then, by > extended my core classes in local classes to preserve the receiver names in > the manifest.
Yes. Basically, the class name is part of the public API of an app widget, and you cannot change the public API of pretty much anything without running into issues. It'd be nice if there were a way for app widgets to be identified by a custom action string in an <intent-filter>, so refactoring could be easier and less risky, but that's not an available option AFAIK. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.7 Available! -- 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
