Nidonocu - typeof(Tea) - All Comments

Twitter Trackbacks for WPF - Themes and Control Libraries - Part 2 - Nidonocu - typeof(Tea) [windowsclient.net] on Topsy.com

Mon, 10 May 2010 11:38:18 GMT

Pingback from Twitter Trackbacks for WPF - Themes and Control Libraries - Part 2 - Nidonocu - typeof(Tea) [windowsclient.net] on Topsy.com

re: SizeToContent border bug

Jason — Wed, 04 Mar 2009 15:05:40 GMT

That is exactly what I was seeing. Although on Windows 2003 (and probably XP) the problem is a lot more noticeable.

Thanks again,

Jason

re: WPF - Themes and Control Libraries - Part 2

mario — Fri, 25 Apr 2008 23:57:59 GMT

is it possible to use the theme's resource dictionary to store resources ( let's say a color resource which has a different value on different themes)

and then reference this resource to acheive the following effect:

on each theme the element will have different colors.

and what does this line do:

DefaultStyleKeyProperty.OverrideMetadata(typeof(CustomButton), new FrameworkPropertyMetadata(typeof(CustomButton)));

re: SizeToContent border bug

Doug Day — Tue, 15 Apr 2008 16:25:29 GMT

Actually, it doesn't "Clip" anything. WPF works in arbitrary units, not pixels, so when displaying your controls on-screen, it has to "cast-down" to pixels to display the object.

In many cases, this can cause a shearing effect, when the object can't figure out which pixel it wants to draw in. In your case, your window border resided "in-between" pixels, and the WPF system decided to draw on BOTH pixels in order to display properly.

SnapsToDevicePixels forces the render mechanisms in WPF to avoid this behavior, and to choose one-or-the-other when rendering objects. In many cases, this can clean up the look quite a bit.

Thanks,

-Doug