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.
Shouldn't the constructor Android.Graphics.Color(int argb) be uint argb.
Why? Java doesn't have unsigned types, and Android/Java is using `int` to hold colors. Consequently, any members that we haven't changed to Color from `int` will continue to be `int` (as that's what Java is using).
Consequently, there must be a Color(int) constructor to assist using members that we've overlooked in the binding customization process.
I suppose we could provide a Color(uint) constructor overload, but I'm not seeing the usecase for it.
Answered in Comment 1