Readme Limitations on Handling Complex Gerbers Suggestion

[ihartwig]

I'm not sure how to word it in the readme, but I think this is a workaround worth documenting. If you open each layer/gerber file of the design in gerbv (File>Open layer(s)...) then resave it (File>Save active layer as...) gerbv will write the same geometry but in a format that gerbmerge can understand. I was using this method to handle the round pads created by Upverter's gerber output as noted in this gist. Thanks for continuing to work on this script!

[rusefillc]

hello @ihartwig

Mostly just saying 'hi' since you are part of the amazing fork chaing

https://github.com/rusefi/gerbmerge forked from unwireddevices/gerbmerge forked from ihartwig/gerbmerge forked from provideyourown/gerbmerge

An interesting fact about the chain: as of today, each fork fully includes the upstream one, i.e. for instance unwireddevices adds to ihartwig fixes

My OCD is wondering if removal of some of these forks would make overall gerbmerge on GH simpler. My understanding of GH repo removal process is that relationships between repos would stay alive?