Mapping those Altium layers to new user layers in KiCad would be a good 
solution for our issue.

Op maandag 25 augustus 2025 om 12:54:46 UTC schreef [email protected]:

> Yeah, it would be a pain to have to remap each footprint one at a time 
> using the layer remapping dialog.  Now that we have unlimited layers in 
> V10, maybe we should map each Altium layer that does not directly map to a 
> KiCad layer to a new User_# layer.
> On 8/25/25 8:46 AM, 'Seth Hillbrand' via KiCad Developers wrote:
>
> This is for footprints, not projects.  So the mapping wizard wouldn't apply
>
> Seth
>
> [image: KiCad Services Corporation Logo]
> Seth Hillbrand 
> *Lead Developer* 
> +1-530-302-5483 <(530)%20302-5483>‬ 
> Long Beach, CA 
> www.kipro-pcb.com    [email protected] 
>
>
> On Mon, Aug 25, 2025 at 5:46 AM Wayne Stambaugh <[email protected]> 
> wrote:
>
>> Seth,
>>
>> Isn't someone working on an import wizard for V10 that would address this 
>> issue (Roberto maybe)?  The Eagle importer allows users to remap layers 
>> that do not directly map to a KiCad layer which the import wizard would add 
>> to all third party board importers.
>>
>> Wayne
>> On 8/25/25 8:07 AM, 'Seth Hillbrand' via KiCad Developers wrote:
>>
>> This could be a user preference.  You are welcome to make a merge request 
>> adding this preference panel. 
>>
>> An additional external file is probably a non starter 
>>
>> Seth
>>
>> [image: KiCad Services Corporation Logo]
>> Seth Hillbrand 
>> *Lead Developer* 
>> +1-530-302-5483 <(530)%20302-5483>‬ 
>> Long Beach, CA 
>> www.kipro-pcb.com    [email protected] 
>>
>> On Mon, Aug 25, 2025, 1:26 AM Zenn Geeraerts <[email protected]> wrote:
>>
>>> 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
>>>  
>>> <https://groups.google.com/a/kicad.org/d/msgid/devlist/2845e6f5-be42-4e14-a8c0-c848f95d32f1n%40kicad.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>> -- 
>> 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/CAFdeG-qj%2Bsw1c%2Bf6n1rcG%2BopgQgda1SmFpD3v3wj7%3DRAYq_8_Q%40mail.gmail.com
>>  
>> <https://groups.google.com/a/kicad.org/d/msgid/devlist/CAFdeG-qj%2Bsw1c%2Bf6n1rcG%2BopgQgda1SmFpD3v3wj7%3DRAYq_8_Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> -- 
>> 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/1acdc11a-7120-4ae8-9d39-430f615260b2%40gmail.com
>>  
>> <https://groups.google.com/a/kicad.org/d/msgid/devlist/1acdc11a-7120-4ae8-9d39-430f615260b2%40gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> -- 
> 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/CAFdeG-rDB3y79HcXGHr1%2BbA_SSCP5qA0mBViPikhSvhMXutGdA%40mail.gmail.com
>  
> <https://groups.google.com/a/kicad.org/d/msgid/devlist/CAFdeG-rDB3y79HcXGHr1%2BbA_SSCP5qA0mBViPikhSvhMXutGdA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
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/b67b8ddf-b7cf-44b5-a721-8b6aee6b5af2n%40kicad.org.

Reply via email to