kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #03660
Re: Patch to fix a boundary box bug [4 Attachments]
-
To:
<kicad-devel@xxxxxxxxxxxxxxx>
-
From:
Rob Frohne <rob.frohne@...>
-
Date:
Tue, 17 Nov 2009 08:46:21 -0800
-
In-reply-to:
<b845d95d0911170616w3b5bc897p4a5cc501a0b77dd8@...>
-
Organization:
Walla Walla Universisty
-
Reply-to:
rob.frohne@...
-
User-agent:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090817 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
Thanks Brian,
This behavior has bothered me a lot as well. I think your patches will
improve things.
How do you make the boundary boxes visible? I have had a lot of trouble
selecting things with the present method because I would have to guess
what things might be in the selection box and I was usually wrong.
Seeing the box helps a lot.
Also, I took a look at the code to see if we could have a control left
click keep selecting items and add them to the selected list. I got
sidetracked on this task, but I still think it would be a big help as
well. It appears your skills are better than mine. You might want to
look at it too. :-)
Rob
Brian Sidebotham wrote:
> [Attachment(s) <#TopText> from Brian Sidebotham included below]
>
> Hi Guys,
>
> The "bug" that I am seeing is that text fields are included in a
> component boundary box, even if they are invisible. This might have
> something to do with the fact that I have the "Value" field invisible
> in these components as I used Field 1 as the real component value. I
> think it makes more sense to exclude invisble text fields from the
> components boundary box. Some wiring was hard or impossible for me to
> select. I don't think this patch will have any negative effect, and
> invisible elements shouldn't be in the bounding box.
>
> The patch ignores all component fields that are invisble in
> GetBoundaryBox()
>
> Thinking a bit further, do the fields need to be in the component
> boundary box at all? I can see places where I might have some fields
> that would stop me selecting wires because they increase the part's
> boundary box beyond the pin+graphic extents. I tried excluding all
> text fields, and it appeared to work fine for me, selection of
> everything was easy and the accuracy of selection should be best by
> excluding all text fields.
>
> I have attached some screen shots of the boundary boxes for the
> different options.
>
> Best Regards,
>
> Brian.
>
>
--
Rob Frohne, Ph.D., P.E.
E.F. Cross School of Engineering
Walla Walla University
100 SW 4th Street
College Place, WA 99324
(509) 527-2075 http://people.wallawalla.edu/~rob.frohne
--------------000204070006060700030906 Content-Type: text/x-vcard; charset="utf-8"; name="frohro.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="frohro.vcf"
begin:vcard
fn:Rob Frohne
n:Frohne;Rob
org:Walla Walla University;Engineering
adr:;;100 SW 4th Street;College Place;WA;99324;USA
email;internet:rob.frohne@...
title:Professor
tel;work:509 527 2075
x-mozilla-html:FALSE
url:http://people.wallawalla.edu/~rob.frohne/
version:2.1
end:vcard
--------------000204070006060700030906--
Follow ups
References