Pattern editor does not respect paste masking

[mpaalanen]

I have created a footprint for the Tag-Connect PCB pattern with 6 surface pads for the connector pogo pins.
On an ENIG plated board i don't want these pads to have solder so i masked them in the pattern pad settings.

Screenshot 2024-04-25 102928.png (28.39 KiB) Viewed 8248 times

Whatever i do, that masking is not properly effected on the PCB.
However, if define the pads identically on the PCB, it works as expected.
I have verified several times over that i have correctly attached the pattern to the component, updated the component in the schema, and the schema to the PCB. That way it just does not work.

[Alex]

When you update a board from a schematic, existing mask/paste settings of patterns on the board have higher priority than those settings from components in the schematic.
The solution is to delete the pattern on the board. Then update the board from the schematic.
Alternatively, you can edit mask/paste settings directly in PCB Layout.

[dominicc]

I ran into the same issue and noted that if they had already been changed in the board layout, then diptrace won't update the settings when you update from schematic after changing settings in the library.

Silently ignoring the change is confusing.

This is different, from when say a 3D model changes, and diptrace shows a dialog showing what changed (i.e. the 'use schematic models' prompt)

This behavior is far from ideal, as when you do a new revision of a PCB, the workflow should be to go back to the patterns used by ALL PCBs, then fix the issues you found in the first revision of the PCB, then you update all your PCB revisions that use the patterns. The problem is then that it's extremely difficult to track which designs used which patterns and thus which need updating.


Perhaps it would be good if the 'update from schematic' didn't actually update the board, but instead presents you with a dialog that shows a list of components, and the properties of them, that are about to be changed, with old/new values, with a default of 'accept' next to each, which the user can change to 'deny' as appropriate. and ideally with a 'remember' tickbox, so that future updates remember the setting that was used so that when the next update occurs, the default for the 'accept/deny' for the property that is to be changed comes from the update when 'remember' was checked.

See attached GUI mockup.

dialog-idea-1.png (38.05 KiB) Viewed 7914 times