I kind of enjoy the French names. It keeps me on my toes! Besides,
AFAIK it's the last of the French strings in KiCad. When I joined the
project most of the source code comments were in French. I'm the one
who translated them all to English so I could work on the project. I
actually thought
Yes Wayne, thanks.
JP, it's all your fault, demos shouldn't have proprietary Frenchy layer
names. :D
I think the demos should have proper layer names, I forgot the layer names
could be changed because I almost never go to Layer Setup.
It would be confusing for beginners when looking at demo
Copper layers can be renamed so I only expect the layer names F.Cu and
B.Cu when I have not renamed them. I'm guessing you have one of the
kicad demo projects open based on the French layer names which JP likes
to use.
On 2/25/2018 8:59 PM, Andrey Kuznetsov wrote:
> Not sure if this is the right
Not sure if this is the right thread that dealt with Layers tab, but anyone
else thinks the first 2 names should say:
F.Copper
B.Copper
instead of:
[image: Inline image 1]
On Sat, Feb 17, 2018 at 3:04 PM, Andrzej Wolski
wrote:
> There is a simple fix to this problem,
There is a simple fix to this problem, patch in attachment. It needs to
be applied on top of this patch:
https://bugs.launchpad.net/kicad/+bug/1743890
Witch this patch there is another issue: when all layers (in Layer tab)
are hidden, anchors and invisible text are still displayed.
I'm not
On 2018-02-08 07:02 AM, kristoffer Ödmark wrote:
for example, disbling rendering of front footprints disables all the F.Silk,
F.Fab, adhesive and many more.
Disabling the rendering of Text on the front only disables text belonging to
a footprint, no other. Basically the Render tab does not do
I think it has been mentioned before about potentially creating user
defined visibility settings that could be added to the layer manager
context menu. I'm guessing that we would have to rework some of the
underlying code to make this possible. It's definitely something to
keep in mind for
As you noticed, one can only define simple layer visibility dependencies
in GAL using SetRequired() method. Effectively, you can quickly disable
a whole layer when another is invisible, but it does not handle well
cases of e.g. texts whose visibility should depend both on the layer and
the parent
I started investigating this some more, there is much more rendering
problems here.
for example, disbling rendering of front footprints disables all the
F.Silk, F.Fab, adhesive and many more.
Disabling the rendering of Text on the front only disables text
belonging to a footprint, no other.
On 2018-02-07 04:25 PM, Wayne Stambaugh wrote:
If you use legacy renderer then turn off Pads Front and Pads Back under
the Render tab on the right the pads disappear. If you are in GAL mode
they remain visible.
Given that the legacy canvas will hopefully be removed in the v6
development
On 2/7/2018 4:24 PM, Kevin Cozens wrote:
> On 2018-02-07 04:04 PM, Wayne Stambaugh wrote:
>> I agree with you on this. I don't know why the layer setting is ignored
>> and the pads are shown anyway but it's always been this way. I would
>> rather the logic be to respect the layer setting.
>
>
On 2018-02-07 04:04 PM, Wayne Stambaugh wrote:
I agree with you on this. I don't know why the layer setting is ignored
and the pads are shown anyway but it's always been this way. I would
rather the logic be to respect the layer setting.
If you use legacy renderer then turn off Pads Front
Hey!
Another confusion arised when I was speaking to a friend. When disabling
the F.Cu layer, the pads are still visible. I can understand the need to
be able to disable the pads on the front layer separate from everything
else, to check for things under pads etc.
What I cannot understand
13 matches
Mail list logo