X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Mon, 25 Jul 2016 04:18:14 +0200 (CEST)
X-X-Sender: igor2 AT igor2priv
To: "Brane2 (brane2 AT s5tehnika DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] pcb: polygon "twin hole" bug - fixed
In-Reply-To: <a4770e13-ae66-aff4-843d-36923cc254b1@s5tehnika.net>
Message-ID: <alpine.DEB.2.00.1607250415590.7286@igor2priv>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1607070651120 DOT 7286 AT igor2priv> <4f9dfd62-45cd-a307-a6d9-93b7cd4333a2 AT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1607241855150 DOT 7286 AT igor2priv> <f9211aa4-f13e-8ce6-171b-9abf3e5faab0 AT s5tehnika DOT net> <1efdee06-c218-7cac-4029-4f42e420ec82 AT s5tehnika DOT net>
 <582b39fe-fc83-7b80-8e9c-95459f5b8b1e AT s5tehnika DOT net> <a4770e13-ae66-aff4-843d-36923cc254b1 AT s5tehnika DOT net>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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



On Mon, 25 Jul 2016, Brane2 (brane2 AT s5tehnika DOT net) [via geda-user AT delorie DOT com] wrote:

> On 25. 07. 2016 02:54, Brane2 (brane2 AT s5tehnika DOT net) [via 
> geda-user AT delorie DOT com] wrote:
>
> <SNIP>
>> Also, If i start drawing hole over several polygons that partially cover, 
>> like top and bottom layer, for some reason hole will stick to polygon on top 
>> layer, even if I happen to be on the bottom layer at that time.
> Errm, scratch that last part. Now this works.
>
> But I was definitely able to f**k this up once or twice and triggered polygon 
> copy to some obscure layer. It seems that it is possible to screw up operation 
> internal state for all future holes by lucky selection of first hole. I did it 
> once, but can't repeat it now.

I have high hopes for r2309 fixing this too: if the first click's search 
didn't result in any polygon (user clicked far away from polygons) the 
code went into invalid state: hole drawing activated with no polygon 
chosen.

>
> Anyhow, it seems much better than it was.

Thanks!


Regards,

Igor2