O derp.

A fix was applied to deal with out of bounds dxf last week to 8.0

https://gitlab.com/kicad/code/kicad/-/issues/18523

On Tue, Nov 26, 2024, 6:32 AM Rafał Pietrak <[email protected]>
wrote:

> Moja,
>
> Just explaining:
>
> there are two sides to this case. The one that you've noticed, when one
> uses such feature to scale up/down the design, which is obviously not
> the case for PCB artworks. But the other case is the control of the
> design resolution, which in fact I had in mind. In short: whenever you
> change the grid size, you keep the physical design size the same, but
> influence the "rounding errors" of your artwork. ... and frankly, that's
> exactly what I personally prefer.
>
> -R
>
> On 26.11.2024 12:09, Mojca Miklavec wrote:
> > On Tue, 26 Nov 2024 at 06:06, Rafał Pietrak <[email protected]>
> wrote:
> >>
> >> Guys, have you ever considered going to "virtual dimensions"?
> >>
> >> What I mean here is that the entire design (that is the PCB of course,
> >> not the SCH) is based on an integer grid like "natural numbers indices
> >> to locations", while the grid size is provided for the entire PCB as a
> >> single float?
> >
> > Please note that I'm not familiar with KiCad code, but I fail to see
> > how this could possibly work (other than introducing an unnecessarily
> > complicated workflow).
> > This might work well for art where you draw some nice graphic of an
> > animal, and you only decide how big the graphic should be when you
> > export it/save it/print it.
> >
> > When you instead load a component footprint, you need to know its
> > exact dimensions. Let's say that a courtyard should for example be
> > precisely 1 mm = 1,000,000 nm wide.
> > If you suddenly decide that you need a PCB that is 7.5 m wide instead
> > of 5 m, so that a unit is 1.5 nm instead of 1 nm ... what do you do?
> > Do you just end up with all your components being 1.5 mm wide and with
> > the wrong pitch? Or do you keep transforming the coordinates every
> > time you change your mind about how big your scaling factor should be?
> > Should the courtyard then shrink to 1,000,000 / 1.5 = 666,667 units
> > (and you basically end up with something way worse than floating point
> > numbers)?
> >
> > Mojca
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "KiCad Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/a/kicad.org/d/msgid/devlist/338d9f47-d6ea-48b4-a682-b6241237f219%40electric-sheep.eu
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/kicad.org/d/msgid/devlist/CAJjB1q%2Bm8tUuPv2AKBqTNhX6bXRPfO1p34g6ucsDXY1sP%3DaGmw%40mail.gmail.com.

Reply via email to