Hi Cirilo,
thanks anyway for pointing out this useful patch!
Hi Wayne, could this patch be committed to the stable release?
bye,
Maurice
On 6/17/15 1:23 AM, Cirilo Bernardo wrote:
Hi Maurice,
It's not my patch; that's the work of Jeppe Johansen.
- Cirilo
On Wed, Jun 17, 2015 at 8:14 AM,
Hi Cirilo,
I object! :P
I think I mainly agree with your points.
In [1] you can find (a draft/ WIP ) of a UML model I design for the 3dparsers,
in [2] there is a structure architecture that I design to handle VRML/X3D. That
is a simplification of the specification and it have in mind to handle
Thanks Mario,
I'll have a look at the documents you've written. This is a tricky one
since I plan to make substantial changes to the code currently handling
3D models; I wouldn't want you to do too much work only to find that
everything needs to be refactored. On the other hand I don't know
how
Hi Cirilo,
As I explained, in my point if view there is no point to do "substantial
changes". From the analysis I did, I find lots of things that then are missing
or desired so the proper way will be rewrite from rewrite from scratch a new
proper solution. Otherwise it will be constructing a ca
On 6/17/2015 3:53 AM, ea...@katamail.com wrote:
> Hi Cirilo,
>
> thanks anyway for pointing out this useful patch!
>
> Hi Wayne, could this patch be committed to the stable release?
I believe JP committed it in r5764.
>
> bye,
> Maurice
>
> On 6/17/15 1:23 AM, Cirilo Bernardo wrote:
>> Hi M
yes!
thanks JP and all! :)
Maurice
On 17/06/2015 14.46, Wayne Stambaugh wrote:
On 6/17/2015 3:53 AM, ea...@katamail.com wrote:
Hi Cirilo,
thanks anyway for pointing out this useful patch!
Hi Wayne, could this patch be committed to the stable release?
I believe JP committed it in r5764.
Le 17/06/2015 00:11, Chris Pavlina a écrit :
> 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
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) a
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 GetBody
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 a
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
You probably saw my thread about the bounding boxes for LIB_TEXT and
LIB_FIELD, which were being merged with the main component bounding box
incorrectly. I tracked down what the bug was:
in ::GetBoundingBox(), the coordinates are inverted because "Y
coordinates for LIB_ITEMs are bottom to top".
Le 17/06/2015 19:35, Chris Pavlina a écrit :
> You probably saw my thread about the bounding boxes for LIB_TEXT and
> LIB_FIELD, which were being merged with the main component bounding box
> incorrectly. I tracked down what the bug was:
>
> in ::GetBoundingBox(), the coordinates are inverted be
Hi,
I'd like to know if it would be possible to add Ellipse support in DXF
import function in pcbnew...
I tried to import a pcb board shape from a DWG file:
http://www.tekoenclosures.com/multimedia/manuali/dwg/MOK1.dwg
then I exported the DWG to DXF ASCII 2013 with TeighaFileConverter (as
sugg
Fixes a discrepancy between legacy and GAL described in this bug:
https://bugs.launchpad.net/kicad/+bug/1462810
Double clicking on a DRC error now zooms in to the marker. I choose a magic
number for the zoom level (90) that seemed pretty similar to the legacy
zoom level.
Thanks,
Jon Neal
diff --g
2015-06-18 3:02 GMT+02:00 Marco Hess :
> Hi Maurice,
>
> If in LibreCAD you take your file and then do a 'Save As' in 'DXF R12'
> Format (in the Save As dialog at the bottom "Save as type", it forces
> LibreCAD to save in a older DXF format that does not support ellipses and
> converts them to line
Hi,
When using version control, I noticed that whenever I safe the file,
almost every line changed, even if there are only tiny changes. This
is very annoying, in particular with version control, as it is
impossible to see what changed (also it makes it virtually impossible
to merge changes manuall
17 matches
Mail list logo
