Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Probably the reason it isn't working is what is commonly referred to as "Airspace" issues. Basically the code you're using is rendering pixels with GDI and WPF is implemented with DirectX, and the two rendering technologies don't know how to share pixels. There may be something more subtle also happening, but at first glance I suspect that's it.</p> <p>The way you'd want to do this in WPF is similar to what Mranz suggested before. There are a couple simple ways to get the blur effect with WPF:</p> <ol> <li><p>Create two text blocks directly on top of each other (e.g. in a grid occupying the same cell) both with the same font and text, etc, but make the bottom one have the color you want for glow and then apply a blur effect on it. You need to be careful that without the effect they are both rendering the same way or the blur will be off.</p></li> <li><p>Create an ellipse, or a rectangle with ellipses at the edges, and do the same trick of putting it behind the textblock with the title and put a blur effect on it.</p></li> </ol> <p>It's a bit tricky also because Windows changed some of these behaviors between Vista and 7 (and I have no idea what 8 is ultimately going to look like). If I remember correctly, in Vista when you maximized the window the blur effect would go away and the font color would turn white. In 7 that doesn't happen anymore. In at least the developer preview of 8 (and Office 2010) the title text is now centered. Also when you're doing this yourself you need to be careful about not obscuring the caption buttons because it probably won't start clipping the text at the place you'd expect.</p> <p>If you have problems with either of those approaches feel free to ping me. I can probably put together some sample code but I don't have the styles handy. Also if you solve it, please post your solution so others can benefit :)</p> <p>Hope that helps,</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload