MIME-Version: 1.0
In-Reply-To: <1356866711.18718.2.camel@localhost>
References: <1356866711 DOT 18718 DOT 2 DOT camel AT localhost>
Date: Sun, 30 Dec 2012 23:14:34 +1100
Message-ID: <CAN-_CWxCk96Nyk=kRYdEX7qAstMR6X3YsX0qBtb8K54=pK-5NA@mail.gmail.com>
Subject: Re: [geda-user] Split "find" colouring now in git HEAD
From: Geoff Swan <shinobi DOT jack AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=f46d04430446f5365004d210d6fd
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk

--f46d04430446f5365004d210d6fd
Content-Type: text/plain; charset=ISO-8859-1

I completed a new board layout with this over the last couple of days. The
split coloring is fantastic. It makes clear the difference between routed
and 'needs to be routed'. Eg. I thought I'd connected up a section but had
missed adding a the thermal relief to a via/poly connection.
This would've looked connected using my previous work flow.
It also gives a better sense for progress on a large net such as ground.
Thanks heaps for this change - it is something I use constantly during
layout.

--f46d04430446f5365004d210d6fd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>I completed a new board layout with this over the last couple of days. T=
he split coloring is fantastic. It makes clear the difference between route=
d and &#39;needs to be routed&#39;. Eg. I thought I&#39;d connected up a se=
ction but had missed adding a the thermal relief to a via/poly connection. =
<br>

This would&#39;ve looked connected using my previous work flow.<br>
It also gives a better sense for progress on a large net such as ground.<br=
>
Thanks heaps for this change - it is something I use constantly during layo=
ut.<br>
</p>

--f46d04430446f5365004d210d6fd--