Hi all We are trying to load Altium footprints into KiCad but noticed that some mechanical layers from Altium get merged into 1 layer in KiCad. This is caused by these lines:
m_layermap.emplace( ALTIUM_LAYER::MECHANICAL_14, Eco2_User ); m_layermap.emplace( ALTIUM_LAYER::MECHANICAL_15, Eco2_User ); m_layermap.emplace( ALTIUM_LAYER::MECHANICAL_16, Eco2_User ); When removing these lines and changing some of the mappings in the enum, we could get our desired result. In the source code, first the m_layermap is searched and then the enum mappings are used as a fall back. Would it be a good idea to define these mappings in a file so users can choose which Altium layers to convert to which KiCad layers? If no file is used or the Altium layer is not present in the file, search the layermap, then use the enum as a last resort. I could make a merge request for this change if you're interested. Kind regards, - Zenn -- You received this message because you are subscribed to the Google Groups "KiCad Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/kicad.org/d/msgid/devlist/2845e6f5-be42-4e14-a8c0-c848f95d32f1n%40kicad.org.
