On Sun, Mar 20, 2011 at 10:54 AM, Jay Bloodworth
<[email protected]> wrote:
> I have Activity A starting Activity B with an explicit intent. If
> Activity B has no constructor, I get an InstantiationException. With an
> empty nullary constructor, it starts up fine. Activity A (started from
> the debugger) has no constructor but does not give an error. Can someone
> explain the underlying logic behind these cases? Is the empty
> constructor for Activity B the "right" solution? It seems kind of kludgy
> and arbitrary.

You never implement a constructor on an activity.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training...At Your Office: http://commonsware.com/training

-- 
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

Reply via email to