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=subject:to:references:from:message-id:date:user-agent:mime-version
         :in-reply-to:content-transfer-encoding;
        bh=2sKZdAZj3h3QlkgnsWW5ULpl4Qeal2AaNdHi0yu9LAY=;
        b=iLnX1tzxwWJUXFkCHbDM8e2XSMIKpaIAUI9AtkIbvAx7FgpSIFZqdNZQeurImhAC0v
         W9LmBHX+h84qsti/NzlCZe/XtGdqnxGhfGn69Kqxvb8kXXbtNxTCWhNkOcPPy3Y/w5KG
         voY0ISDqTubcEkYJcyWZ34ODM/Bi1hoPAzA5CJEkjkSxu+OMZvQMGxwmrDXXSE+TdpvZ
         SRHSQicV2TyWuttbdqx/rQYvte8yWHz2tw2HRK87Uv0/p2lX4r/omqa3EFfxeN6aJERV
         vSOOVh5ISytN0pl6drcTCSq15vq/89paOFXfPB1UCRhZ6B/MEjVg+V77PQi50f8zr34E
         SckA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:subject:to:references:from:message-id:date
         :user-agent:mime-version:in-reply-to:content-transfer-encoding;
        bh=2sKZdAZj3h3QlkgnsWW5ULpl4Qeal2AaNdHi0yu9LAY=;
        b=B0Pvf22kxbA6AML4ru3Td/eF4P62QjU70rTiDdqTCWhlEyyHeHVJICX1uMA4iOgM8G
         aikQ1MjR9uUi7on//n/u4W3UronrL6ndGKz2GnKXwAwKN/SvQmfT6kTGOqcrjWAe1pZ/
         33A8s67lGsZZpymQT0X+G162outF1ZJik4ebAWP9i+1DL9gtiJo6DGoZ7y6555kihcYC
         0N+/QSeAPL8rSDeUS+vBJuPjQ9YiUOjcoDZ1RqjExNDHEz8cTlPb/r5a0GD7LnefQHt8
         S/yh6qRHPpCR+X1VqlHaOOesqfP34axQ/mlO9ltEzpTJK2S85ZJs++CI68hDR+L4dMYL
         w/cA==
X-Gm-Message-State: ALyK8tJAl68FhAqUA1ElF1elvlOzw47ivnqF36JXMpv5LNbW0qDznzvOJATv28IR9pnV/A==
X-Received: by 10.66.62.226 with SMTP id b2mr66801867pas.119.1468946794741;
        Tue, 19 Jul 2016 09:46:34 -0700 (PDT)
Subject: Re: [geda-user] pcb: polygon "twin hole" bug
To: geda-user AT delorie DOT com
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1607070651120 DOT 7286 AT igor2priv>
From: "Charles Repetti (charlie94965 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <4f9dfd62-45cd-a307-a6d9-93b7cd4333a2@gmail.com>
Date: Tue, 19 Jul 2016 09:46:32 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0)
 Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.00.1607070651120.7286@igor2priv>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
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

Confirmed.

- Charlie


On 7/6/16 10:01 PM, gedau AT igor2 DOT repo DOT hu wrote:
> Hi all,
>
> Evan found a bug in pcb-rnd which turned out to be a bug in mainline 
> as well. It is really easy to reproduce from scratch:
>
> 1. draw a poly
> 2. draw a hole in it (strange: first click ignored?)
> 3. keep on drawing the second hole (strange: marker is not moved?)
> 4. bug: the poly of step 1 is duplicated (copied in place), and the 
> new hole is created on the new poly
>
> Important: do not switch tool between step 2 and 3! This, together 
> with the fact that it can be reproduced with both HIDs suggests it's a 
> bug in core (the strangenesses are maybe related to handling of the 
> mode variable, I have no idea how the poly gets dupped).
>
> Detecting the duplication polys:
>
> - save before and after step 4, compare the two save files; instead of 
> one poly object with two holes there are two poly objects with one 
> hole each
>
> - move the poly after step 4; expected: moving one poly; what happens 
> instead: moving the top poly, leaving the bottom poly in place
>
> - in step 3 draw the second hole so that it has an intersection with 
> the first; that intersection is the only copper hole at the end, 
> because it is not covered by any of the polygons
>
> In pcb-rnd I am still knee-deep in the conf rewrite, but I plan to 
> look at this bug after I finish. In case someone debugs this in 
> mainline, I'm interested in the result. Else I can share my 
> findings/patches when I get to it, so mainline developers can fix this 
> in mainline.
>
> Regards,
>
> Igor2
>
>