<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Built to Spec</title>
	<atom:link href="http://www.built-to-spec.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.built-to-spec.com/blog</link>
	<description>Making Cool Stuff</description>
	<lastBuildDate>Sat, 04 Feb 2012 15:54:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on The Cricut Seems to Be Ripe For the Hacking by Dodi Callander</title>
		<link>http://www.built-to-spec.com/blog/2010/02/14/the-cricut-seems-to-be-ripe-for-the-hacking/comment-page-1/#comment-4636</link>
		<dc:creator>Dodi Callander</dc:creator>
		<pubDate>Sat, 04 Feb 2012 15:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.built-to-spec.com/blog/?p=177#comment-4636</guid>
		<description>For whoever has completely dissected an expression:

I dropped my expresison, and at first it seemed that only the communication port was damaged.  My hubby,being electronically inclined, got a new port and soldered it onto the board.  Unfortunately, he broke the trace and now it does not communicate at all.  To top it off, the size dial no longer works and none of the cricut resets fix this. He took the whole thing apart, made sure the little circuit board on the dial was pushed in all the way, but no luck.

Anyone out there know another fix for the size dial and where the trace from the com port goes?  If we could fix the com port the size dial would not be necessary because of the design studio software.

Thanks,

Dodi</description>
		<content:encoded><![CDATA[<p>For whoever has completely dissected an expression:</p>
<p>I dropped my expresison, and at first it seemed that only the communication port was damaged.  My hubby,being electronically inclined, got a new port and soldered it onto the board.  Unfortunately, he broke the trace and now it does not communicate at all.  To top it off, the size dial no longer works and none of the cricut resets fix this. He took the whole thing apart, made sure the little circuit board on the dial was pushed in all the way, but no luck.</p>
<p>Anyone out there know another fix for the size dial and where the trace from the com port goes?  If we could fix the com port the size dial would not be necessary because of the design studio software.</p>
<p>Thanks,</p>
<p>Dodi</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why I  by tolomea</title>
		<link>http://www.built-to-spec.com/blog/2011/03/25/why-i/comment-page-1/#comment-4630</link>
		<dc:creator>tolomea</dc:creator>
		<pubDate>Sat, 04 Feb 2012 01:41:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.built-to-spec.com/blog/?p=488#comment-4630</guid>
		<description>this one is better

module assembly(debug=false){
    if(debug){
        union(){
            color([1,0,0,1]){
                for(i=[0:$children-1]){
                    for(j=[0:$children-1]){
                        if(i != j){
                            intersection(){
                                child(i);
                                child(j);
                            }
                        }
                    }
                }
            }
            color([1,1,0,0.5]){
                for(i=[0:$children-1]){
                    child(i);
                }
            }
        }
    }else{
        union(){
            for(i=[0:$children-1]){
                child(i);
            }
        }
    }
}

assembly(debug=true){
    cylinder(r=10,h=20,center=true);
    translate([-15,0,0]) cylinder(r=10,h=10,center=true);
    translate([15,0,0]) cylinder(r=10,h=10,center=true);
}</description>
		<content:encoded><![CDATA[<p>this one is better</p>
<p>module assembly(debug=false){<br />
    if(debug){<br />
        union(){<br />
            color([1,0,0,1]){<br />
                for(i=[0:$children-1]){<br />
                    for(j=[0:$children-1]){<br />
                        if(i != j){<br />
                            intersection(){<br />
                                child(i);<br />
                                child(j);<br />
                            }<br />
                        }<br />
                    }<br />
                }<br />
            }<br />
            color([1,1,0,0.5]){<br />
                for(i=[0:$children-1]){<br />
                    child(i);<br />
                }<br />
            }<br />
        }<br />
    }else{<br />
        union(){<br />
            for(i=[0:$children-1]){<br />
                child(i);<br />
            }<br />
        }<br />
    }<br />
}</p>
<p>assembly(debug=true){<br />
    cylinder(r=10,h=20,center=true);<br />
    translate([-15,0,0]) cylinder(r=10,h=10,center=true);<br />
    translate([15,0,0]) cylinder(r=10,h=10,center=true);<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why I  by Craig</title>
		<link>http://www.built-to-spec.com/blog/2011/03/25/why-i/comment-page-1/#comment-4628</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Fri, 03 Feb 2012 17:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.built-to-spec.com/blog/?p=488#comment-4628</guid>
		<description>Oh, I like the idea of taking the intersection of objects in an assembly to detect overlapping components...</description>
		<content:encoded><![CDATA[<p>Oh, I like the idea of taking the intersection of objects in an assembly to detect overlapping components&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why I  by tolomea</title>
		<link>http://www.built-to-spec.com/blog/2011/03/25/why-i/comment-page-1/#comment-4622</link>
		<dc:creator>tolomea</dc:creator>
		<pubDate>Thu, 02 Feb 2012 20:54:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.built-to-spec.com/blog/?p=488#comment-4622</guid>
		<description>Some tools support for assemblies would be nice. I&#039;m kind of new at this, but I had this idea overnight that might help you. It&#039;s a drop in replacement for union that you can use whenever you are assembling parts. Normally it should be about as efficient as union. If you set the debug flag it will instead show you any overlaps.

module assembly(debug=false){
	union(){
		for(i=[0:$children-1])
		{
			if(debug){
				for(j=[0:$children-1]){
					if(i != j){
                                                            echo(&quot;bob&quot;, i, j);
						intersection(){
							child(i);
							child(j);
						}
					}
				}
			}else{
				child(i);
			}
		}
	}
}</description>
		<content:encoded><![CDATA[<p>Some tools support for assemblies would be nice. I&#8217;m kind of new at this, but I had this idea overnight that might help you. It&#8217;s a drop in replacement for union that you can use whenever you are assembling parts. Normally it should be about as efficient as union. If you set the debug flag it will instead show you any overlaps.</p>
<p>module assembly(debug=false){<br />
	union(){<br />
		for(i=[0:$children-1])<br />
		{<br />
			if(debug){<br />
				for(j=[0:$children-1]){<br />
					if(i != j){<br />
                                                            echo(&#8220;bob&#8221;, i, j);<br />
						intersection(){<br />
							child(i);<br />
							child(j);<br />
						}<br />
					}<br />
				}<br />
			}else{<br />
				child(i);<br />
			}<br />
		}<br />
	}<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why I  by Craig</title>
		<link>http://www.built-to-spec.com/blog/2011/03/25/why-i/comment-page-1/#comment-4620</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Thu, 02 Feb 2012 16:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.built-to-spec.com/blog/?p=488#comment-4620</guid>
		<description>Yes, I haven&#039;t looked into completely automating it.  I have had plans to add coloring to the various components and &quot;vitamins&quot; used in my assemblies to make the various components a little easier to recognize and hopefully make it a bit easier to spot intersections.</description>
		<content:encoded><![CDATA[<p>Yes, I haven&#8217;t looked into completely automating it.  I have had plans to add coloring to the various components and &#8220;vitamins&#8221; used in my assemblies to make the various components a little easier to recognize and hopefully make it a bit easier to spot intersections.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

