Bugfixes #105
Bugfixes #105
Conversation
…rough x=0,y=0) change (net <net> "name") to (net <net>) (net_name "name") more concise code in the via section copy net for SUBPOLYINDEX region from master Polygon use heuristic to determine which polygons are apparently overidden by associated regions, or else kicad pours too much. this seems to be a kicad limitation, but manual fix is very easy. bugfixing done working this board: https://shop.trenz-electronic.de/trenzdownloads/Trenz_Electronic/Modules_and_Module_Carriers/4x5/4x5_Carriers/TE0706/REV03/HW_Design/AP-TE0706-03.zip
|
btw, i started learning PCB design a couple of weeks ago, i don't own altium. so don't see this as professional advice. the subpolyindex scheme is not optimal, but leaving it out would also not be. in both cases, manual fixes are likely necessary (just changing nets, no drawing). which can be expected from users of this tool of course. to do it right, geometric analysis must associate a subpolyindex region with a pour polygon, the right one (this should be pretty easy, the idea is that there would be substantial vertex and edge overlap between the 2). i will send a proper fix soon for this. |
|
also note that this patch inverts the mapping of pour index and zone priority. 100 - pour_index = kicad_priority seems to be the right choice to me, but review that please |
|
@thesourcerer8 i am sure kicad-devel would love to hear about it. Their altium importer does not handle subpolyindex and creating these intricate polygon shapes by hand is laborious. |
|
Long ago, when I saw the first few files, I thought that pour_index is between 0 and 100, but then suddenly I got files with a pour_index far outside that range, so I did didnt had a good idea anymore how to properly handle them, and what their meaning really is. |
|
just leave the pourindex conversion out. But it seems obvious to me that 0 has the highest priority for altium for a couple of reasons. with kicad we know that higher numeric value has higher priority. I don't have altium so i cannot confirm it. If you see values above 100, that probably means altium allows a bigger range of values and 100 is the upper limit as per convention only. |
* get board outline and coordinate origin from the pcbdoc * default to no thermal reliefs for now * use kicad6 island_removal * use some regions that have seemingly illegal length fields
|
Can anyone with an Altium license check the meaning of positive and negative priorities please? |
see commit message