Bug 1368 - Android.Graphics.Drawables.BitmapDrawable.ConstantState: wrong property
Summary: Android.Graphics.Drawables.BitmapDrawable.ConstantState: wrong property
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 1.0
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-10-08 16:30 UTC by Atsushi Eno
Modified: 2011-10-09 13:53 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Atsushi Eno 2011-10-08 16:30:16 UTC
android.graphics.drawable.BitmapDrawable#getConstantState() is a property righr now, but it should be a method.

The reason: android.graphics.drawable.Drawable#getConstantState() is a (virtual) method and it does *not* become a property in the managed class because ConstantState is a name for a nested type in Drawable. If getConstantState() becomes a property ConstantState, it results in CS0102, so we don't convert it to a property (which is the right solution).

But, then, BitmapDrawable#getConstantState() should not become a property either, but it actually does (bug in the API generator). Since our old smcs somehow fails to check these member name overlap (our laest mcs doesn't), it ended up to pass to become part of the API now.
Comment 2 Atsushi Eno 2011-10-09 13:53:23 UTC