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 object visibility.

Perhaps we should define visibility rules per class and not per layer,
so we can check additional conditions.


On 02/08/2018 01:02 PM, kristoffer Ödmark wrote:
> 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. Basically the Render tab does not do
> what it says at all.
> A lot of this seems to because of what is set in pcb_draw_panel_gal.cpp:417
> There is a lot of SetRequired-> (layer, layer)
> And that implementation seems broken, could someone shed some light on
> the purpose there?
> On 2018-02-07 22:32, Kevin Cozens wrote:
>> 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 cycle, I guess this issue will go away.
>> True, but I wanted to point out that as far as I was concerned it
>> hasn't always been this way. I would still expect the pads to
>> disappear if I turn off display of front and back pads.
>> [Oops. Sending again as I meant to send it to the list.]
> _______________________________________________
> Mailing list:
> Post to     :
> Unsubscribe :
> More help   :

Attachment: signature.asc
Description: OpenPGP digital signature

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to