<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Now you see it, now you don&#8221;t. Digital assets in XSI.</title>
	<atom:link href="http://www.xsi-blog.com/archives/100/feed" rel="self" type="application/rss+xml" />
	<link>http://www.xsi-blog.com/archives/100</link>
	<description>People and thoughts behind XSI in production...</description>
	<pubDate>Tue, 06 Jan 2009 07:42:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: David</title>
		<link>http://www.xsi-blog.com/archives/100#comment-15591</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 02 Aug 2007 03:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.xsi-blog.com/?p=100#comment-15591</guid>
		<description>I normally just hid unwanted objects with a group and removed all parameters from the keyable parameters panel.  This worked quite well, and still left some flexibility to add or remove parameters for animation. :P</description>
		<content:encoded><![CDATA[<p>I normally just hid unwanted objects with a group and removed all parameters from the keyable parameters panel.  This worked quite well, and still left some flexibility to add or remove parameters for animation. :P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ajlan altug</title>
		<link>http://www.xsi-blog.com/archives/100#comment-14745</link>
		<dc:creator>ajlan altug</dc:creator>
		<pubDate>Tue, 20 Mar 2007 02:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.xsi-blog.com/?p=100#comment-14745</guid>
		<description>Unfortunately, attribute and operation disabling in XSI needs some more work. Locking nodes don't function the way one fancies they should. One good example for a working system would be from Maya where any node can be locked from it's root level on down, or attributes for that matter.  In XSI however, if you are in need of say locking a camera in place. you have to resort to locking it on all levels, not some. So, after doing so, if you want to leave, say rotoscoping free, you don't have the option... In my experience at least...

AJ</description>
		<content:encoded><![CDATA[<p>Unfortunately, attribute and operation disabling in XSI needs some more work. Locking nodes don&#8217;t function the way one fancies they should. One good example for a working system would be from Maya where any node can be locked from it&#8217;s root level on down, or attributes for that matter.  In XSI however, if you are in need of say locking a camera in place. you have to resort to locking it on all levels, not some. So, after doing so, if you want to leave, say rotoscoping free, you don&#8217;t have the option&#8230; In my experience at least&#8230;</p>
<p>AJ</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernard Lebel</title>
		<link>http://www.xsi-blog.com/archives/100#comment-3589</link>
		<dc:creator>Bernard Lebel</dc:creator>
		<pubDate>Thu, 22 Jun 2006 01:30:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.xsi-blog.com/?p=100#comment-3589</guid>
		<description>Hey Andy,

Thanks a lot for the tips. I toyed a little with the SetCapabilityFlag, I can see how it could be used to hide things from the reckless users. I wasn''t aware of these features, thanks a lot for discussing them.


Cheers
Bernard</description>
		<content:encoded><![CDATA[<p>Hey Andy,</p>
<p>Thanks a lot for the tips. I toyed a little with the SetCapabilityFlag, I can see how it could be used to hide things from the reckless users. I wasn&#8221;t aware of these features, thanks a lot for discussing them.</p>
<p>Cheers<br />
Bernard</p>
]]></content:encoded>
	</item>
</channel>
</rss>
