replaces depreciated / obsolete SKMatrix.PreConcat method #692
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Details
Replaces the depreciated / obsolete method SKMatrix.PreConcat Method.
Related Issue
Motivation and Context
Just out of curiosity I wanted to check how many (obvious) changes need to be made to update SkiaSharp to version 3.
During compilation the only issue that cropped up was the usage of this method. So I replaced it.
Since the changes are also valid with version 2.88 I thought I'd make a PR for it. Maybe a tiny bit less to worry about when you really make the switch.
Aside: Of course vvvv didn't run with the "updated" standard libs.
Types of changes
Docs change / refactoring / dependency upgrade
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
My change requires a change to the documentation