Yeah, I know that much - I'm just trying to figure out where the
LIB_TEXT bounding boxes are going /wrong/. Try it - turn on the switch
to view the bounding boxes (sch_component.cpp line 382, recommend
changing GetBoundingBox on 385 to GetBodyBoundingBox, it's a bit more
helpful in this case)
I'm looking into it, anyway, just wanted to know if anyone knew much
about it. There's always the possibility that I misunderstood something,
since I'm working in a section I haven't been in before, so I'd rather
dive into it myself than waste your time. I'll submit a patch if there
really is
For the curious, have a look at this bizarre screenshot:
http://misc.c4757p.com/bbox_wtf.png
I turned on drawing of bounding boxes for both component bodies and
LIB_TEXTs - the text's bounding box renders correctly, but it merges
with the rest of the component drawing item boxes wrong, growing
Le 17/06/2015 17:39, Chris Pavlina a écrit :
Yeah, I know that much - I'm just trying to figure out where the
LIB_TEXT bounding boxes are going /wrong/. Try it - turn on the switch
to view the bounding boxes (sch_component.cpp line 382, recommend
changing GetBoundingBox on 385 to
Hi all,
While working on that field autoplace feature, I noticed that
LIB_PART::GetBodyBoundingBox was returning incorrect bounding boxes when
the parts contained a LIB_TEXT. Further investigation revealed that
there was an extra negation of the vertical dimension somewhere in the
mix. The
5 matches
Mail list logo
