>> The code seems to implement the [one group per copper layer], but
>> that seems...odd, especially in view of the grouping it implies.
> It's intended to group copper drawing layers into copper physical
> layers.

That was my impression - so it seems a bit odd to group silk and copper
together (which is how it seems to be done in both thermal.pcb and
tut1.pcb, the two files I've been using as test cases).

>> [...] soldermask layers [...]?
> Old topic.  [...] nobody has done the work [...].

Gotcha.

>> It looks as though the only way to change max_layer is to create or
>> load a new board.  Right?
> Or add layers to or delete layers from the current board.

How is that done?  I searched the code for assignments to either
max_layer or LayerN and didn't find any except in new-board and
load-board code.  What did I miss?

If you have the leisure and inclination to explain a little more, I'd
like to get my head around route styles a bit more.  (If not, you can
stop reading now, as the rest of this message is about them.)

So far, they appear to be just ways to tag collections of four distance
settings to make it easy to switch between them.  The questions are
about the details.  (The devil is, as usual, in the details.)

It appears to me that there are "live" values for these four settings,
which are stored in Settings, and NUM_STYLES (why always this many?
more legacy code?) in PCB->RouteStyle[].  It appears to me that the
design calls for ways to copy from RouteStyle[] to Settings and from
Settings to RouteStyle[], to change which element of RouteStyle[] is
`current' (ie, affected by the former two), and to change arbitrary
RouteStyle[] values.  The things that aren't clear to me are:

- Is there always a `current' RouteStyle[] slot?  That is, does the
   design expect that changing the Settings values will affect the
   current RouteStyle[] slot's values too, and conversely?

- What is the "style" HID flag?  It appears to be something like the
   `current' value mentioned above, but not quite; its use in
   set_some_route_style() (core file.c) is cryptic.  The comment is
   clear enough, as far as it goes; what's obscure is how checking the
   HID flag determines whether "the current one" happens to match
   anything.  I can't see any code that checks Settings against
   RouteStyles[] and updates the "style" flag upon finding a match, so
   I must be missing _something_ - what?

/~\ The ASCII                           der Mouse
\ / Ribbon Campaign
 X  Against HTML               [EMAIL PROTECTED]
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B


_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

Reply via email to