Bug 60354 - [Enhancement] Update CGAffineTransform public fields to match native property names
Summary: [Enhancement] Update CGAffineTransform public fields to match native property...
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 11.4 (d15-5)
Hardware: Macintosh Windows
: Normal enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
Depends on:
Reported: 2017-10-24 18:43 UTC by John Miller [MSFT]
Modified: 2017-10-25 08:40 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 for Bug 60354 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description John Miller [MSFT] 2017-10-24 18:43:26 UTC
## Overview

The native CGAffineTransform[1] uses properties a,b,c,d,tx,ty while the Xamarin.iOS CGAffineTransform[2] uses xx,xy,yx,yy,x0,y0 names. 

It's preferable that the names of the Xamarin.iOS CGAffineTransform match the native types so that documentation is easier to understand when working with Xamarin.iOS. 

[1] https://developer.apple.com/documentation/coregraphics/cgaffinetransform
[2] https://developer.xamarin.com/api/type/MonoMac.CoreGraphics.CGAffineTransform/
Comment 1 John Miller [MSFT] 2017-10-24 18:49:44 UTC

Wrong link for [2]. It should be:

Comment 2 Rolf Bjarne Kvinge [MSFT] 2017-10-25 08:40:02 UTC
We can't change existing names (to maintain backwards compatibility), but we might consider adding additional properties that just calls the existing ones.

I wonder if this is something we can do with extensions once (if?) C# has support for "extension everywhere" (https://github.com/dotnet/csharplang/issues/192)