Hi all,
Right now, we have conflicting "desired order" for technical layers in
various places.
The layer widget displays "front first", i.e. F.Paste before B.Paste, F.Fab
before B.Fab, etc.
Everywhere else in the codebase is "back first".
This leads to this bug: https://bugs.launchpad.net/kicad/
Why is it Front and Back, as opposed to Top and Bottom?
Front/Top should be first.
On Wed, Jan 10, 2018 at 8:50 PM, Jon Evans wrote:
> Hi all,
>
> Right now, we have conflicting "desired order" for technical layers in
> various places.
>
> The layer widget displays "front first", i.e. F.Paste be
Regarding Front vs Top, I see it called Top everywhere else, but back to
the original question: +1 for Top/Front first.
Thanks,
Diego
On Thu, Jan 11, 2018 at 5:52 AM, Andrey Kuznetsov
wrote:
> Why is it Front and Back, as opposed to Top and Bottom?
> Front/Top should be first.
>
> On Wed, Jan 1
Yes, in the KiCad codebase, they are called Front and Back, and my question
is independent of whether or not they should be called Top and Bottom :-)
On Thu, Jan 11, 2018 at 2:16 PM, Diego Herranz <
diegoherr...@diegoherranz.com> wrote:
> Regarding Front vs Top, I see it called Top everywhere els
Actually, programs like Altium and Allegro allow you to swap the order of
layers, to change visibility of transparent layers.
For example, make back layer have higher priority, and front layer lower
priority, with the back layer setting to 50% transparency, etc.
But I guess this layer manager is g
My original question is about the structure of the kicad code, not about
the layer manager. I'm asking if there is any technical reason why back
layers are listed first in a specific part of the code base. If no one has
a good answer, I'm going to submit a patch to change it to have front
layers fi
6 matches
Mail list logo
