<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blackkettle &#187; XAML</title>
	<atom:link href="http://blog.blackkettle.org/category/coding/xaml/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.blackkettle.org</link>
	<description>Things of Occasional Interest</description>
	<lastBuildDate>Wed, 10 Feb 2010 16:03:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>You Don&#8217;t Need A Meaningful API If You&#8217;ve Got Meaningful Error Messages</title>
		<link>http://blog.blackkettle.org/2007/02/14/you-dont-need-a-meaningful-api-if-youve-got-meaningful-error-messages/</link>
		<comments>http://blog.blackkettle.org/2007/02/14/you-dont-need-a-meaningful-api-if-youve-got-meaningful-error-messages/#comments</comments>
		<pubDate>Tue, 13 Feb 2007 23:46:49 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[WPF]]></category>
		<category><![CDATA[XAML]]></category>

		<guid isPermaLink="false">http://blog.blackkettle.org/2007/02/14/you-dont-need-a-meaningful-api-if-youve-got-meaningful-error-messages/</guid>
		<description><![CDATA[Woo, long time no update.
Anyhoo, in my WPF explorations today, I managed to trigger this little gem:
System.ArgumentOutOfRangeException : '100' is not a valid
Percent value for a KeyTime. The Percent value must be a number
from 0.0 to 1.0.

What the hell were they thinking?
]]></description>
			<content:encoded><![CDATA[<p>Woo, long time no update.</p>
<p>Anyhoo, in my WPF explorations today, I managed to trigger this little gem:</p>
<pre><code>System.ArgumentOutOfRangeException : '100' is not a valid
Percent value for a KeyTime. The Percent value must be a number
from 0.0 to 1.0.</code></pre>
</p>
<p>What the hell were they thinking?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blackkettle.org/2007/02/14/you-dont-need-a-meaningful-api-if-youve-got-meaningful-error-messages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Updated the Lexicon</title>
		<link>http://blog.blackkettle.org/2006/09/11/updated-the-lexicon/</link>
		<comments>http://blog.blackkettle.org/2006/09/11/updated-the-lexicon/#comments</comments>
		<pubDate>Mon, 11 Sep 2006 09:59:29 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Shaxam]]></category>
		<category><![CDATA[XAML]]></category>

		<guid isPermaLink="false">http://blog.blackkettle.org/2006/09/11/updated-the-lexicon/</guid>
		<description><![CDATA[Just made a quick update to the Lexicon page.  In a nutshell, it turns out that you can animate PerspectiveCameras in exactly the same way as Model3Ds, because they support a Transform property.  I haven&#8217;t had a chance to play with it properly yet, but it means no more fiddling with Vector3DAnimations to [...]]]></description>
			<content:encoded><![CDATA[<p>Just made a quick update to the <a href="http://blog.blackkettle.org/lightwave-winfx-lexicon/">Lexicon page</a>.  In a nutshell, it turns out that you can animate PerspectiveCameras in exactly the same way as Model3Ds, because they support a Transform property.  I haven&#8217;t had a chance to play with it properly yet, but it means no more fiddling with Vector3DAnimations to change LookDirection any more.  Woohoo!</p>
<p>Oh, and it looks like the same applies to Lights.  More Woohoo!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blackkettle.org/2006/09/11/updated-the-lexicon/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Confused about Normals</title>
		<link>http://blog.blackkettle.org/2006/08/28/confused-about-normals/</link>
		<comments>http://blog.blackkettle.org/2006/08/28/confused-about-normals/#comments</comments>
		<pubDate>Mon, 28 Aug 2006 11:52:19 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Shaxam]]></category>
		<category><![CDATA[XAML]]></category>

		<guid isPermaLink="false">http://blog.blackkettle.org/2006/08/28/confused-about-normals/</guid>
		<description><![CDATA[For some reason, the Normals property on a MeshGeometry3D is per vertex.  Who ever heard of a point having a normal?  It&#8217;s weird.  Just thought I&#8217;d point that out.
]]></description>
			<content:encoded><![CDATA[<p>For some reason, the Normals property on a MeshGeometry3D is per vertex.  Who ever heard of a point having a normal?  It&#8217;s weird.  Just thought I&#8217;d point that out.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blackkettle.org/2006/08/28/confused-about-normals/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>We got flayed!</title>
		<link>http://blog.blackkettle.org/2006/08/16/we-got-flayed/</link>
		<comments>http://blog.blackkettle.org/2006/08/16/we-got-flayed/#comments</comments>
		<pubDate>Wed, 16 Aug 2006 08:02:21 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[LightWave]]></category>
		<category><![CDATA[Shaxam]]></category>
		<category><![CDATA[XAML]]></category>

		<guid isPermaLink="false">http://blog.blackkettle.org/2006/08/16/we-got-flayed/</guid>
		<description><![CDATA[The post is here.
]]></description>
			<content:encoded><![CDATA[<p>The post is <a href="http://flay.com/GetDetail.CFM?ID=2312">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blackkettle.org/2006/08/16/we-got-flayed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mapping Video</title>
		<link>http://blog.blackkettle.org/2006/08/12/mapping-video/</link>
		<comments>http://blog.blackkettle.org/2006/08/12/mapping-video/#comments</comments>
		<pubDate>Sat, 12 Aug 2006 13:06:28 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[LightWave]]></category>
		<category><![CDATA[XAML]]></category>

		<guid isPermaLink="false">http://blog.blackkettle.org/2006/08/12/mapping-video/</guid>
		<description><![CDATA[So, I&#8217;m trying to map a video texture onto a Xaml surface. So far, so easy. Except I want to apply the diffuse data to the emissive channel, because that&#8217;s closer to the way LightWave works. This is fine with static textures, but there&#8217;s a problem with videos. I generate as much as possible in [...]]]></description>
			<content:encoded><![CDATA[<p>So, I&#8217;m trying to map a video texture onto a Xaml surface. So far, so easy. Except I want to apply the diffuse data to the emissive channel, because that&#8217;s closer to the way LightWave works. This is fine with static textures, but there&#8217;s a problem with videos. I generate as much as possible in a ResourceDictionary, and the relevant Xaml looks a little like this:</p>
<pre><code>&lt;VisualBrush x:Key="media_element" Opacity="1.0"&gt;
  &lt;VisualBrush.Visual&gt;
    &lt;MediaElement Source="#filename#" /&gt;
  &lt;/VisualBrush.Visual&gt;
&lt;/VisualBrush&gt;
&lt;DiffuseMaterial Brush="{StaticResource media_element"} /&gt;
&lt;EmissiveMaterial Brush="{StaticResource media_element"} /&gt;
</code></pre>
<p>The problem is that even when I specify that the DiffuseMaterial and EmissiveMaterial brushes point to the same element, they get their own players which don&#8217;t start in sync, so you get ghosting and funky audio ringing. I can&#8217;t see an obvious way around this&#8230; Anyone?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.blackkettle.org/2006/08/12/mapping-video/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
