Bug 150 - CoreGraphics API should use properties instead of setter methods
Summary: CoreGraphics API should use properties instead of setter methods
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 4.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2011-08-02 17:27 UTC by Jeffrey Stedfast
Modified: 2011-09-23 09:56 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 Jeffrey Stedfast 2011-08-02 17:27:12 UTC
CGContext has setter methods like SetLineWidth(), SetStrokeColor(), etc which should probably all be Properties.
Comment 1 Sebastien Pouliot 2011-09-23 09:56:36 UTC
There is no 'getter' for most of CGContext Set* methods and it's against FXDG to use properties with only setters (and would break the API or add a bunch of [Obsolete]).