Amazingly it didn't though, it was working for quite some time until I
changed something and then it broke. I guess it's a race condition of
some kind.
Peter
On Oct 2, 6:01 pm, hackbod <[EMAIL PROTECTED]> wrote:
> You shouldn't do work in the constructor, because the activity class
> is not ini
You shouldn't do work in the constructor, because the activity class
is not initialized until onCreate() is called.
The code you quote should fail every single time the activity is
constructed.
On Oct 2, 3:55 pm, PAS <[EMAIL PROTECTED]> wrote:
> It seems like the R.string resource is not availab
The second one is the way its meant to be. I don't know the exact
reason but its probably similar to the fact why there are no
Constructors for Activities, but the onCreate()/onDestroy()/onResume()
Lifecycle-Stuff.
Regards, plusminus
http://anddev.org
# Worlds largest Android Development Communi
3 matches
Mail list logo
