Unless we can figure out how to set the grid origin using a single
origin, I don't see how we can get rid of it. One thing we have done a
poor job of is providing an easy way to clear the grid origin. I would
like to see a reset grid origin menu entry.
On 5/18/19 2:22 PM, Jeff Young wrote:
> I
I agree that we want one movable origin, but I don’t think we need two. The
local origin should work fine for placing components relative to each other,
routing, etc.
> On 18 May 2019, at 18:59, Reece R. Pollack wrote:
>
> Once you establish a base coordinate origin, you really don't want
Once you establish a base coordinate origin, you really don't want that
moving. All the mechanical holes, notches, connectors, switches,
clearances, and other locations are measured from that origin. Moving
during layout risks placing a component in the wrong spot.
The movable grid origin is
Hi Eeli,
I’d argue that you explained what it was useful for, not why it is “needed”. I
can understand offsetting the grid; I can’t say I believe it’s important enough
to support the code and UI complexity that it brings.
Cheers,
Jeff.
> On 18 May 2019, at 14:12, Eeli Kaikkonen wrote:
>
>
Am 2019-05-18 08:13, schrieb Tomasz Wlostowski:
On 13/05/2019 12:58, jp charras wrote:
Perhaps also adding a parameter like (circle_optimization [low,
normal,
high] to optimize shapes with arc/circle items (perhaps useful in
microwave applications)
I'm OK with it. Seth?
Yes. Since the
la 18. toukok. 2019 klo 13.38 Jeff Young (j...@rokeby.ie) kirjoitti:
> We need fewer origins.
>
> I like the name Coordinates Origin, but why do we then need a Grid
> Origin? And why a setting for the displayed coordinates? Shouldn’t that
> always be the Coordinates Origin?
>
> Cheers,
> Jeff.
Comments from the peanut gallery:
“Coordinates Origin” sounds clunky and feels redundant. Coordinates are always
relative to some origin. I like “Grid Origin” if it’s a choice between the two
names. Displayed coordinates and a displayed grid should always agree on (0, 0)
IMHO, so there’s no
On 13/05/2019 12:58, jp charras wrote:
> If we are talking about V6.0 version, we should add zone property field
> in the file format like (outline_thickness 0.0) to avoid serious issues
> (generating broken boards for fabrication).
>
Hi JP,
Are you going to work on this (commit code)?
>
On 16/05/2019 20:44, Jon Evans wrote:
> I can think of at least two alternatives:
>
> 1) automatic performance tuning based on self-benchmarking
>
> 2) a "graphics performance" setting (high/medium/low) that changes
> multiple things under the hood.
Hi Jon,
I'm afraid this would be difficult
Hello, Jeff!
On 18/05/2019 12.37, Jeff Young wrote:
> We need fewer origins.
I agree.
> I like the name Coordinates Origin, but why do we then need a Grid Origin?
> And why a setting for the displayed coordinates? Shouldn’t that always be
> the Coordinates Origin?
My imagination of the
We need fewer origins.
I like the name Coordinates Origin, but why do we then need a Grid Origin? And
why a setting for the displayed coordinates? Shouldn’t that always be the
Coordinates Origin?
Cheers,
Jeff.
___
Mailing list:
11 matches
Mail list logo
