X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Taoc0jUTN/KpX8P7HHLZwlM7qFkFFgBRR1yqORZeH/0=; b=EU2yZ5KCSHU/l0nsoSOKmagLGkukDg4wl6UzkKrg1vh1LAlTccFgaH/VHiVMY+gDJA UcEgdHE7mIsE4Rcmoz2IznTcyP/Xsigc12DfrfAzKYmEy8HumtejCQ3+lcWsheuLX3EE f+lGAs2cgyUFUs+VE3wqUIE05GaOKvkig8aqhmzL7RiPlwVEQqOt90WcHzi0Xu5AQC6d NtMeA5q87cO7lB8Ty0zaoJst3MaNnL6KqLKCneVbbisUkYFK2foLkvs1psWchhOjgLIs nHbBbRwtjHhQXRQ1SqwvYR30MzT2BIeOWBZCIR6nKjg+4+uN/4QAfeyaGMixOxToKsAQ 2w4A== MIME-Version: 1.0 X-Received: by 10.180.89.101 with SMTP id bn5mr13772228wib.20.1444097561039; Mon, 05 Oct 2015 19:12:41 -0700 (PDT) In-Reply-To: References: <560F9AC7 DOT 3040607 AT jump-ing DOT de> <5610FEF9 DOT 5050307 AT jump-ing DOT de> Date: Mon, 5 Oct 2015 18:12:40 -0800 Message-ID: Subject: Re: [geda-user] making DRC less misleading in the presence of shorts, non-routed rats, etc. From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=f46d0444eba325a07c0521662a1b 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 --f46d0444eba325a07c0521662a1b Content-Type: text/plain; charset=UTF-8 On Mon, Oct 5, 2015 at 4:15 PM, Kai-Martin Knaak wrote: > Britton Kerin (britton DOT kerin AT gmail DOT com) [via > geda-user AT delorie DOT com] wrote: > > >> I'd try to catch the output of AddAllRats() into a buffer for > >> displaying it in the DRC window. Perhaps only the first 1024 bytes or > >> something. Some new GUI code, reuse of short-checking code, mission > >> accomplished. > >> > >> BTW., this will also check for missing connections, which are certainly > >> also a reason to not send a board to the manufacturer. > > > > > > Yes, I said so already. > > Ok, so I might have misunderstood you on the original post. I had the > impression, you were about to issue a warning in the DRC window no matter > what. Now, it seems to me more like an actual check and a text warning in > the DRC window if a short is detected. Does this paraphrase your branch > correctly? > If so, I'd be very happy to see this hit git/head! > Sadly no, I was just stating that I was aware of the missing connection issue as well as the short issue, and that the warning message I added addresses both. I completely agree that the message I propose is not a perfect solution, but still maintain its better than nothing and priorities should go elsewhere. This is a non-issue for users who already know how it works, it's just trying to remove one small trap for noobs. I don't think its worth getting too obsessed with the perfect fix. Britton --f46d0444eba325a07c0521662a1b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Mon, Oct 5, 2015 at 4:15 PM, Kai-Martin Knaak <= knaak AT iqo DOT un= i-hannover.de> wrote:
Britton Kerin (britt= on DOT kerin AT gmail DOT com) [via
geda-user AT delorie DOT com] wrote:<= br>
>> I'd try to catch the output of AddAllR= ats() into a buffer for
>> displaying it in the DRC window. Perhaps only the first 1024 bytes= or
>> something. Some new GUI code, reuse of short-checking code, missio= n
>> accomplished.
>>
>> BTW., this will also check for missing connections, which are cert= ainly
>> also a reason to not send a board to the manufacturer.
>
>
> Yes, I said so already.

Ok, so I might have misunderstood you on the original post. I had th= e
impression, you were about to issue a warning in the DRC window no matter what. Now, it seems to me more like an actual check and a text warning in the DRC window if a short is detected. Does this paraphrase your branch
correctly?
If so, I'd be very happy to see this hit git/head!

Sadly no, I was just stating that I was aware of= the missing connection issue as well as the short issue, and that the warn= ing message I added addresses both.=C2=A0 I completely agree that the messa= ge I propose is not a perfect solution, but still maintain its better than = nothing and priorities should go elsewhere.=C2=A0 This is a non-issue for u= sers who already know how it works, it's just =C2=A0trying to remove on= e small trap for noobs.=C2=A0 I don't think its worth getting too obses= sed with the perfect fix.=C2=A0

Britton=

--f46d0444eba325a07c0521662a1b--