X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Subject: Re: [geda-user] Net length info question
To: geda-user AT delorie DOT com
References: <0a59af1c-d27e-2b2f-f649-fd5f84ae7fc5 AT linetec DOT nl>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1802031633270 DOT 12270 AT igor2priv>
 <b9ab4067-447e-9d0b-42ba-1f4cbd5aaeb5 AT linetec DOT nl>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1802031733570 DOT 12270 AT igor2priv>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1802032002380 DOT 12270 AT igor2priv>
 <CAJZxidCATy+AaYGj_=HaXgO6onrMYgYEsC6oxaxacapq8SSMLA AT mail DOT gmail DOT com>
 <e546ac7c-5414-f517-2404-02f9697bd58e AT linetec DOT nl>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1802051320570 DOT 12270 AT igor2priv>
From: "Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <dc53159e-9edc-a034-0b7b-896e4b5cb8d5@linetec.nl>
Date: Mon, 5 Feb 2018 14:02:10 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.00.1802051320570.12270@igor2priv>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Hi Igor,

Op 05-02-18 om 13:25 schreef gedau AT igor2 DOT repo DOT hu:
>
>
> On Mon, 5 Feb 2018, Richard Rasker (rasker AT linetec DOT nl) [via 
> geda-user AT delorie DOT com] wrote:
>
>> Igor has been very kind to implement this in his pcb-rnd, and even 
>> though it has some quirks and limitations(*), it was a great help in 
>> marking fixed 100 mm distances along a path.
>
> Cool, I'm happy you could solve your problem with this quick-hack 
> solution.

Yup, it's definitely a lot easier than manually breaking up lines, 
finding resulting segment lengths, and then counting dots :-)

And it's of course also the (ahem) warm fuzzy Open Source mentality, 
with a feature fix within minutes instead of years (if even that).
The only drawback is that I feel somewhat guilty for hardly contributing 
things myself (apart from some translations), being an end user most of 
the time.
My programming abilities are unfortunately limited to a bit bash/shell, 
and PIC assembly (albeit this last one quite extensively).
I could do some cleaning up up symbols and footprints, but that's only 
useful when done on a large scale, which would gobble up a lot of time.

>> *: it only functions with the cursor over a straight line segment, at 
>> least 40 mils from a local bend point, not over arcs. It also appears 
>> slightly imprecise: it reports different values for the exact same 
>> grid point if the mouse cursor is moved between measurements (I 
>> estimate some 0.2% deviation maximum). And oh, by default, it selects 
>> the local line segment between the local bend points, and it 'Finds' 
>> (green highlight) the path to the right. But it's very useful all the 
>> same.
> Arc: if needed, it's possible to do the same trick for arcs.
>
> Preicision: well, it works as specified/requested: to the cursor (not 
> to the crosshair!). It's possible to modify it to work to the 
> crosshair, if that's needed.

Ah, that'll be it -- I didn't think about the difference (so the one 
being imprecise would be me, then, haha).

> The 40 mil limit: this is the only one that's somewhat hard at the 
> moment. I plan to have a full rewrite of find.c this year (for other 
> reasons), and that will introduce features that will make it simpler 
> to do this sort of searches too, and then the 40 mil limitation could 
> be removed.

Please don't spend too much time on these one-user features ... although 
I can image some other uses, having to do with inductances and 
resistances along track lengths, or the already mentioned memory bus 
applications, with parallel chips each requiring well-specified, 
identical path lengths. So it might have some more uses...

But anyway, thanks again,

Best regards,

Richard