On Wed, Dec 19, 2007 at 04:05:11PM -0800, Ben Jackson wrote: > On Wed, Dec 19, 2007 at 06:40:43PM -0500, DJ Delorie wrote: > > > > Ben, as far as I can tell this is yours. It broke on the 2nd-ish. > > The LayerN patch sounds familiar (we've had this bug before). > > I'll check into it, but the LayerN->max_layer change was to fix a bug > where buffers had LayerN of 0. For the main board, my change just > moves from Data->LayerN (where Data is PCB->Data) to max_layer, which > is PCB->Data->LayerN, so there should be no change.
I bet what's going on is that PCB->Data isn't assigned until after the board loads. If you 'revert' it works fine, because it uses the previously loaded board's value. So in parse_y.y there's an InitClip and I'm guessing PCB->Data->LayerN is not yet yyData->LayerN. I went to max_layer because that seemed to be the trend elsewhere (and since it references the board, it eliminates the need to mess with every buffer when you load a new board). We can certainly change polygon.c back, but I bet either way is wrong for some things. -- Ben Jackson AD7GD <[EMAIL PROTECTED]> http://www.ben.com/ _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
