Given the current state of sanctity of even the comment layer names (for which I can't find a good reason different than "Dick doesn't like it", since copper layers are renameable anyway so most probably in my tree I'll allow it), since most of the work for adding layers is in place (the big thing missing is the module library format AFAIK)...
was taken in account the possibility for completely new user layers in the file format? Especially for the module library. In the sexp board it should be reasonably simple to add a layer (a number and a name in the layer form) but I have no idea about the plans for the module format. Another thing it worries me is how to reconcile different layer choices between libraries, in such case; example: if in, say, slot 50 of a lib I put clearance info, then download a lib where slot 50 has, uhmm, a peeling mask, putting them on a board would be quite a mess. Defining names at a 'system' (like we are doing now) or at a 'user' level (in the global configuration) would certainly make things easier but compromise interoperability with other libraries. A clever idea is needed for this. Dynamically allocated layer numbers maybe? If it sees a new name it add it to the list in memory and indexes it using it. Since layers are seen as a number only in the layer form and after that the layer name is always used it would work. Better ideas? -- Lorenzo Marcantonio Logos Srl _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
