search

mcauser / Fritzing-Part-Micro-Python-pyboard

Fritzing part: MicroPython pyboard
7 stars 0 forks source link

Your version was great until Fritzing got at it #3

Open peterhinch opened 8 years ago

peterhinch commented 8 years ago

In your version of this part it's possible to route traces between pins, and I've successfully developed three boards having this feature. The new version of Fritzing software invites you to 'update' the part to the new version - which I gather is based on your contribution. Unfortunately if you let it do this, existing designs fail the design rules check: their part disallows running tracks between pins on either side of the PCB.

In my view this makes your excellent part unusable in any but the simplest designs. Fortunately I have backups so nothing is lost, but it puzzles me that so many Fritzing parts disallow a practice which has been routine for forty years or more. Evidently they can manufacture such boards. Do you have an opinion on this?

mcauser commented 8 years ago

Sorry Peter, I only just noticed this issue. I'll investigate. The Fritzing team made some modifications to my parts when they added them to their core parts in version 0.9.3b. I believe they broke my WeMos D1 mini part too.

Now that all core parts are managed through GitHub, I can make a PRs with fixes and once merged, can be upgraded when you restart the app.

peterhinch commented 8 years ago

There is a pattern here: many (perhaps all) their existing parts preclude running tracks between pins. Their pin and socket headers have driven me nuts with this one. I think they have some kind of standard going here, based on limitations last seen in backstreet factories in 1965...