You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current dev-version of Fluent ribbon, the icon of the RibbonWindow is blurry again. A similar behavior was already observed and fixed in #50 and #63, however this time, the blurry icon is not stretched. As you can see in the following image, all icons are 16px tall (as expected).
(from left to right: Windows Explorer (correctly rendered icon); .Net 4.0; .Net 4.5)
Judging based on the color of the pixels representing the border, it looks like WPF is trying to move the icon half a pixel upwards. Normally this should be prevented by setting SnapsToDevicePixels="True" - as is already done. Maybe setting the Margin="4,1,0,0" instead of Margin="4,0,0,0" helps, like in #63.
I'm currently unable to test this potential fix myself, since I'm still stuck with VS2013 :/
This behavior is reproducible using the Fluent.Test application. (I used the build from appveyor)
Environment
Fluent.Ribbon v5.0.0-dev0430
Theme Office 2013 (only available)
Windows 7 and 10 1607 (Build 14393.10)
.NET Framework 4.0 and 4.5
DPI-Settings/Scaling 96ppi/100%
The text was updated successfully, but these errors were encountered:
With the current dev-version of Fluent ribbon, the icon of the RibbonWindow is blurry again. A similar behavior was already observed and fixed in #50 and #63, however this time, the blurry icon is not stretched. As you can see in the following image, all icons are 16px tall (as expected).
(from left to right: Windows Explorer (correctly rendered icon); .Net 4.0; .Net 4.5)
Judging based on the color of the pixels representing the border, it looks like WPF is trying to move the icon half a pixel upwards. Normally this should be prevented by setting
SnapsToDevicePixels="True"
- as is already done. Maybe setting theMargin="4,1,0,0"
instead ofMargin="4,0,0,0"
helps, like in #63.I'm currently unable to test this potential fix myself, since I'm still stuck with VS2013 :/
This behavior is reproducible using the Fluent.Test application. (I used the build from appveyor)
Environment
The text was updated successfully, but these errors were encountered: