Bug 15966 - Constructor for Android.Graphics.Color
Summary: Constructor for Android.Graphics.Color
Alias: None
Product: Android
Classification: Xamarin
Component: Bindings ()
Version: 4.8.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2013-11-06 10:43 UTC by brosner
Modified: 2017-06-30 04:26 UTC (History)
2 users (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 brosner 2013-11-06 10:43:50 UTC
Shouldn't the constructor Android.Graphics.Color(int argb) be uint argb.
Comment 1 Jonathan Pryor 2013-11-15 16:09:03 UTC
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.
Comment 2 Chris Hardy [MSFT] 2017-06-30 04:26:57 UTC
Answered in Comment 1