StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I found <a href="http://pagebrooks.com/archive/2009/03/31/bitmap-caching-in-silverlight-3.aspx" rel="nofollow">this link</a> explaining <code>CacheMode</code> in Silverlight 3. From the link: [This link is dead.]</p> <ul> <li>BitmapCache is the only cache-mode that is supported.</li> <li>The Caching is applied to the element and all of it’s child elements.</li> <li>BitmapCaching should be used in scenarios where you are blending, transforming (translating, stretching, rotating).</li> <li>Misuse of the CacheMode feature can hurt performance, so you need to really think through what you are doing. If your visual tree is interleaving cached and un-cached elements, you are effectively causing multiple rendering surfaces to get created behind the scenes. The un-cached surfaces are rendered in software and the cached surfaces are rendered in hardware. Your performance will be best if you can minimize the total number of rendering surfaces and get the hardware to do work where it can.</li> <li>You can determine which elements are being cached by adding the EnableCacheVisualization parameter to your Silverlight plugin declaration. <code><param name="EnableCacheVisualization" value="true" /></code></li> <li>As far as I can tell, GPU acceleration does not occur on Macs when the Silverlight application is not in full-screen mode. This is apparently a limitation of the Safari plug-in model.</li> </ul> <p>I wonder if the <code>EnableCacheVisualization</code> can be enabled for WP7, I'm using <code>BitmapCache</code> for a <code>LongListPicker</code> and a <code>ContentPresenter</code> (that I populate with dynamically created content) and it'd be interesting to know if the caching is working. But according to the 3rd bullet, you should be using it only if you're animating <code>UIElement</code>s, which I'm not, so maybe I shouldn't be using it at all!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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