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 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
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The native CGAffineTransform uses properties a,b,c,d,tx,ty while the Xamarin.iOS CGAffineTransform 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.
Wrong link for . It should be:
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)