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; q=dns/txt; c=relaxed/relaxed;
	d=s5tehnika.net; s=default; h=Content-Transfer-Encoding:Content-Type:
	In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:
	Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From:
	Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:
	List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
	bh=/EjlJGixKlVRvDj13TKhjqX7lBt5ovzX4KQzGendmC8=; b=Nwc00pK/0qscNC4/4i4bcOB6c+
	9Dh7iUAls7PK3AtGnOFnRyeFZ1dlqlCT1bERWXPJUkBibNweZ/bi5Nuqnbv8fg3PmH6Zi3u9aQzwu
	39xSqs9eaYCKD8T6+Od4uDEN3ejlLGu9V4NDIeoduu7GE8OnJhu46U9ADXTSThCDbnW/1+PzUtSYp
	9SboGl8Die4ShYi5+/Djqu195HFmeNOBZt37Y6IQx6GW/n3msMPpoXDJsri2kZT9r3MTtnhfGIxeG
	1d7K0UgZC1Z30uIApDD6Z/4DjKJVfrqbeF3IBrU/tCFUSYb9kwQ4LsjlSQLPiIlnChVsN/bi7RR/9
	WYgOzPkA==;
Subject: Re: [geda-user] pcb: polygon "twin hole" bug - fixed
To: geda-user AT delorie DOT com
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>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1607250415590 DOT 7286 AT igor2priv>
From: "Brane2 (brane2 AT s5tehnika DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <caf173b4-5cc6-cf42-9101-394bca4bb80b@s5tehnika.net>
Date: Thu, 28 Jul 2016 09:09:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.00.1607250415590.7286@igor2priv>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.studiofaca.com
X-AntiAbuse: Original Domain - delorie.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - s5tehnika.net
X-Get-Message-Sender-Via: server.studiofaca.com: authenticated_id: brane2 AT s5tehnika DOT net
X-Authenticated-Sender: server.studiofaca.com: brane2 AT s5tehnika DOT net
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 25. 07. 2016 04:18, gedau AT igor2 DOT repo DOT hu wrote:
>
>
> 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.
Close, but no cigar. Now I can click first point outside polygon, but as 
long as any subsequent hole vertex lands in it, with final vertex hole 
gets created on the polygon, as it should.
Problem is, thing goes berserk if none of the hole vertices actually hit 
the meat of the polygone. Eg. when you draw one hole and after that 
another, within first one.
Or e.g put 4 vias inside poly. Then try to make a hole in poly, that has 
vertices inside via clearances or vias themselves. This situation 
usually arises when you have e.g poly over dip connector and you want to 
get rid of many small, unconnected islands. If you draw a hole over such 
place, chances are all its vertices will hit pins and not enclosing poly 
and thing can do anything from deleting whole poly, to drawing another 
one on some obscure layer ( white silk) or killing itself.

This happens only when placing the hole and program searches for the 
poly to apply it to. Once you place the hole, you can place whatever 
over its vertices, it will be fine.



>
>>
>> Anyhow, it seems much better than it was.
>
> Thanks!
>
>
> Regards,
>
> Igor2
>