-
-
Notifications
You must be signed in to change notification settings - Fork 417
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
Change DPI to 96 #1781
base: main
Are you sure you want to change the base?
Change DPI to 96 #1781
Conversation
Thanks for creating this PR but I am not sure if this would be the best solution. Maybe we could add an extra |
Yeah, okay, that sounds good. |
Will you be going to make these changes or do you want me to do this? |
I don't know anything about how that dpi test would work. I think it would be better if you did it. |
In the unit test you would need to check if the |
/// </summary> | ||
/// <param name="self">The image.</param> | ||
/// <typeparam name="TQuantumType">The quantum type.</typeparam> | ||
/// <returns>A <see cref="WriteableBitmap"/>.</returns> | ||
public static unsafe WriteableBitmap ToWriteableBitmap<TQuantumType>(this IMagickImage<TQuantumType> self) | ||
where TQuantumType : struct, IConvertible | ||
{ |
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 would create a private method that has the current implementation and specify either new Vector(96, 96)
or new Vector(self.Density.X, self.Density.Y)
as an argument to that method.
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 updated it with ToWriteableBitmapInternal
and sending argument between the two.
Fixes #1780