mike wrote:
> We're not communicating. Are you saying that the only time
> I should do a new XX() is *only* in onCreate?
No, we're definitely not communicating.
As I wrote:
1. Never implement a constructor in an Activity.
In Java, "implement" means "to write code".
Your sample code had:
public HelloActivity() {
}
Do not do this in an Activity (or Service, for that matter). Or, as I
also wrote:
2. If you choose to violate rule #1, chain to the superclass.
That would mean adding a call to super() in the otherwise do-nothing
implementation of HelloActivity().
As you pointed out, these flaws did not impact the test case, but they
could have. In fact, I'm kinda surprised the activity survives not
having the activity's constructor called. Gotta look up Activity in the
source code sometime to see what symptoms you'd get for doing that...
> Mike, I'll look at view flipper. View.GONE would be really cumbersome
> and inelegant
:: shrug ::
I think calling setContentView() outside of onCreate() is cumbersome and
inelegant, but, to each their own.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy
Android Consulting/App Development: http://commonsware.com/consulting
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
