-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
An odd "phenomenon" while usage MetroWindow and Canvas. #3638
Comments
@DeputyOfCopyPaster can you upload your sample? I have an idea, but I have to try it tomorrow if it works. Happy coding |
ok, please look at the sample attached. To see difference look first at pure WPF project, then add MetroWindow by yourself and catch the "phenomenon". I really hope you make it! |
@DeputyOfCopyPaster The SnapsToDevicePixels of the MetroWindow is set to true, so all inner controls inherits this value. You can fix this by changing the SnapsToDevicePixels for the Canvas and set it to false. <Canvas SnapsToDevicePixels="False">
</Canvas> |
Hello everyone!
Metro 1.6.5
I've noticed that something wrong happens with images (Canvas) while Metro framework usage.
I performed two simpliest tests and I had been surprised that pure WPF project is deprived of such a "phenomenon" as follows:
In other words the pure WPF project handles well with all Canvases inserted.
So, my question is, how to get rid of that "phenomenon"?
Please any insights on that issue?
thanks in advance!
An Update: the same disaster has v.2.00-alpha0490.
The text was updated successfully, but these errors were encountered: