On Thu, Apr 30, 2009 at 8:55 AM, westmeadboy <[email protected]> wrote:
> > OK, so you said one reason the State is not exposed is because you > don't want client code relying on these States because they are > "inherently transient". > > However, the alternative is for the client code to keep track of this > State, which is no better in this regard. > > Is there another reason not to expose the State? No, the fact that a "getState()" method would be unreliable is reason enough not to have one. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
