Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Android.Util.TypedValue.ApplyDimension takes an int as the first parameter to indicate unit type, but you guys re-factored the unit-type int constants into the ComplexUnitType enumeration in Android.Util, so ApplyDimensions should take the enum parameter instead of the int.
Wow, I didn't know that this complex type is using enums. And while such int->enum conversion should have already been completed in our sources, it actually *wasn't*.
Thanks for the report anyways, I'll fix this in our sources so that this should become enum in the next major release.
The problem is, it even caught in my latest "collect every int-based methods and review everything" work BUT I thought it *is* an int value as there is *no* description on unit parameter saying it uses those constants for whatever converted to ComplexUnitType in the earlier days (before I started to improve enums). And now I cannot be very sure that we're finalizing enum changes.
The review process is still human-dependent which means there will be errors (and unlike others expect there is not really automatic way to verify enum state sanity).