Bug 7832 - CGAffineTransform: Negative scale behaving improperly
Summary: CGAffineTransform: Negative scale behaving improperly
Status: RESOLVED DUPLICATE of bug 19341
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 6.0.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-10-14 16:52 UTC by Bryan Moulton
Modified: 2014-04-29 08:04 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:

Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-10-15 06:18:40 UTC
The C# CGAffineTransform.Scale method multiplies the matrices in the reverse order compared to the ObjectiveC CGAffineTransformScale method.

You can get the expected behavior in C# by doing this:

transform = CGAffineTransform.Multiply (CGAffineTransform.MakeScale (1.0f, -1.0f), transform);

Admittedly this difference is unfortunate, but unfortunately we can't change it now without breaking lots of code.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2014-04-29 08:04:41 UTC
A new overload has been introduced that behaves like the native CGAffineTransformScale function.

See bug #19341 for more information.

*** This bug has been marked as a duplicate of bug 19341 ***