We have an non-written policy about not breaking (aka changing without
the users knowledge) existing boards so I'm going to side with JP on
this one. We should wait and implement this in v6 as a new feature.
Cheers,
Wayne
On 12/8/18 5:33 AM, jean-pierre charras wrote:
> I agree with Seth: this change can create issues with existing boards.
> The best way is to revert it.
>
> The root issue is the fact the margin layer is not yet used in V5.
> I am expecting it will be activated in V6, because its purpose is to define clearance margins, visible and easy to edit and combine with items defined inside a footprint.
>
> Basically using Egde_Cuts both as board outlines (with the constraint to
> define only closed shapes) and to define a clearance margin is a broken
> feature.
>
> The best way is to use margin layer to define clearance margins (and not
> necessary closed shapes, because castellated pads are incompatible with
> a closed shape) and Egde_Cuts only for board outlines .
>
We have an non-written policy about not breaking (aka changing without
the users knowledge) existing boards so I'm going to side with JP on
this one. We should wait and implement this in v6 as a new feature.
Cheers,
Wayne
On 12/8/18 5:33 AM, jean-pierre charras wrote:
> I agree with Seth: this change can create issues with existing boards.
> The best way is to revert it.
>
> The root issue is the fact the margin layer is not yet used in V5.
> I am expecting it will be activated in V6, because its purpose is to define clearance margins, visible and easy to edit and combine with items defined inside a footprint.
>
> Basically using Egde_Cuts both as board outlines (with the constraint to
> define only closed shapes) and to define a clearance margin is a broken
> feature.
>
> The best way is to use margin layer to define clearance margins (and not
> necessary closed shapes, because castellated pads are incompatible with
> a closed shape) and Egde_Cuts only for board outlines .
>