kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #28640
Re: Layer ID enums
-
To:
kicad-developers@xxxxxxxxxxxxxxxxxxx
-
From:
Wayne Stambaugh <stambaughw@xxxxxxxxx>
-
Date:
Sun, 12 Mar 2017 14:06:01 -0400
-
In-reply-to:
<CA+qGbCB2Hq+U4pZs=vgodS61eJv8HThT1MkU0YmS6gVcnNgW7g@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
I cannot speak about the GAL enums but I can tell you that if you muck
up the legacy layer enums, you will almost surely break loading really
old board files. I would proceed with extreme caution here.
On 3/12/2017 12:25 PM, Jon Evans wrote:
> Hi,
>
> Can anyone explain if there is a reason why the layer definition enums
> are done in the way they are?
>
> Using multiple enums for the "normal" layers and the GAL extra layers is
> complicating the code, especially now that I am using the GAL layers for
> GerbView, and also working on a color theme manager that will be shared
> across applications.
>
> It would make more sense to me if there was a single large enum that
> contained all possible layers, with some offset somewhere to separate
> the "drawing" layers from the "GAL item" layers. This would simplify
> code that needs to refer to layer IDs across multiple applications.
>
> Would anyone be opposed to this?
>
> -Jon
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References