X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=UjpHSkgcdpF3aThdpPIErW3rm+1jLFm6nHNqlLtDADQ=; b=CqLH+4DXmbnarCwkcK+3JcWqxQybHPgo+IMlT1T+0z1H+iLJdPQ0bzwQScRqiIImZ/ 22kZkhSwCbQDgTQ/3oAYHgASkDVdvNbtZNwaFXZqwvNax83yGJw6cBG8wv8ZIzPYciHU EFv/zLHvFTM5wi45C2V7ZxV5pPwygAGaE5bzdDbcctyfj9O2Jpa+fuBV/RL4BGkinnzM rP925jT/O6eONpZ07nnzYcVilvzifu0qIe6nu4uTaZpc+dEPllSyFOXrREtKd2RnBUlU enSHpoFiHXDUBEr7PgBl4ks7U5/ujtTQGMAdsGjOcEI7gV3H/NaWCsz5U5BFUNvc1ts9 ywgA== MIME-Version: 1.0 X-Received: by 10.42.63.145 with SMTP id c17mr6335714ici.22.1358522689596; Fri, 18 Jan 2013 07:24:49 -0800 (PST) In-Reply-To: References: <57B44348-7A53-4743-8A60-7C9D31EFD1ED AT noqsi DOT com> <20130117144225 DOT 30d2507f AT svelte> <1DCD2904-101A-4EDF-A5F5-4B137ACD71E8 AT noqsi DOT com> Date: Fri, 18 Jan 2013 13:24:49 -0200 Message-ID: Subject: Re: [geda-user] libgeda circle parsing From: =?UTF-8?Q?Antonio_Todo_Bom_=E2=9C=88?= To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=90e6ba3fcd87552bb704d391b6c2 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 --90e6ba3fcd87552bb704d391b6c2 Content-Type: text/plain; charset=ISO-8859-1 Yes, Nevertheless ... The radius can be zero, but if you have thickness theoretically would be shown on paper. But when I can reach a zero radius circle, it is invisible at the screen. But I see that we left out a bit of the question I asked, as the code. I just mentioned that if the code checks null or negative radius, why he corrects to zero? I think of two things: - Or just check if there are negative radius. - Or correct to a value known as a standard. I'm just saying that I see no sense in the routine check if it is zero, then mention it as a mistake, and then to correct to zero anyway. This was just a moment of philosophy in programming :) Anyway, I sometimes have some invisible entities left across the design. And I think is relevant to "seek and destroy it" , or just turn them visible anyway :D Regards, Antonio --90e6ba3fcd87552bb704d391b6c2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Yes, Nevertheless ...
The radius can be zer= o, but if you have thickness theoretically would be shown on paper. But whe= n I can reach a zero radius circle, it is invisible at the screen.

But I see that we left out a bit of the question I asked, as= the code.

I just mentioned that if the code check= s null or negative radius, why he corrects to zero?

I think of two things:
- Or just check if there are negative= radius.
- Or correct to a value known as a standard.
<= br>
I'm just saying that I see no sense in the routine check = if it is zero, then mention it as a mistake, and then to correct to zero an= yway.

This was just a moment of philosophy in programming =A0= :)

Anyway, I sometimes have some invisible entitie= s left across the design. And I think is relevant to "seek and destroy= it" , or just turn them visible anyway :D

Regards,
Antonio
--90e6ba3fcd87552bb704d391b6c2--