To answer my own question, I have what looks like a workable solution, but I don't love it. Please add your improvements and offer better suggestions, but I'd like to keep this conversation going.
I added a private no arg ctor to the superclass. The createFromParcel method calls this, and then calls a static method on the superclass that takes parameters of that class and a parcel. Subclass Parcelable.CREATORs can do the same thing - create their own instance and then call the superclass.setValues and pass the instance it is creating. There isn't an issue writing the parcel - you can just call super.writeToParcel. This doesn't seem very elegant, and it may be slightly slower. I may have 1 big class instead of splitting it up... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" 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-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
