-
-
Notifications
You must be signed in to change notification settings - Fork 852
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix DrawImage offsetting issues and improve API parameter names. #2474
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is is quite alot of breaking changes..
we have 2 dfferent types of breakign changes happening here, we have the paramater name renames, which is a source breaking change for people using names paramaters.
And then we have the contructor change, which is both a source and binary breaking change.
I am a little less opiniated with regards the source/paramater rename break. i'm not really a fan of breaking them for not a lot of benefit but i can live with them. but we really should not be introducing the binary break.
/// <param name="colorBlendingMode">The blending mode to use when drawing the image.</param> | ||
/// <param name="alphaCompositionMode">The Alpha blending mode to use when drawing the image.</param> | ||
/// <param name="opacity">The opacity of the image to blend.</param> | ||
public DrawImageProcessor( | ||
Image image, | ||
Point location, | ||
Point backgroundLocation, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should add an overload with out the ForegroundRectangle
for back compatability, as this will be an binary breaking change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I always forget these are public.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aproving, but leaving my reservation on changing the paramater names, I would rather we didn't change them and only changed the docs/comments but I won't stand in the way of the change
Thanks, and very much noted. I only changed them because I actually got confused while debugging. I'd like to keep them for v3.1 as I feel they do add benefit. |
Prerequisites
Description
Fixes #2447
In addition, I renamed the parameters and properties in the extension methods and processors to make it obvious what each thing means.