| commit | c1df6f7725601489a1562811ffc0c717a56445f5 | |
| author | Peter Clifton <pcjc2@cam.ac.uk> | |
| Wed, 21 Oct 2009 18:45:05 +0000 (21 19:45 +0100) | ||
| committer | Peter Clifton <pcjc2@cam.ac.uk> | |
| Wed, 21 Oct 2009 18:45:05 +0000 (21 19:45 +0100) | ||
| tree | 10bd21dc7781bdf4134ef7143a26a7737ffc32e7 | treesnapshot (tar.gz zip) |
| parent | 09020e6a57e5e9b901b125ab6c818d626b9f92a5 | commitdiff |
Fix "newfullpoly" flag test and save its state into the .pcb file.
The flag controlling this behaviour is kept up to date as a PCB flag,
not something which is updated in Settings.FullPoly. Change the test
accordingly.
Added a PCB flag "newfullpoly" to save this state in the .pcb file.
NOTE: "full" polygons severly break connectivity checking, as the code
always treats broken up pieces of the polygon as being connected.
It _might_ have been better to leave this support broken - so
users don't inadvertently create polygons with the "fullpoly" flag.
TODO: Consider removing, hiding or adding warnings to this feature.
The flag controlling this behaviour is kept up to date as a PCB flag,
not something which is updated in Settings.FullPoly. Change the test
accordingly.
Added a PCB flag "newfullpoly" to save this state in the .pcb file.
NOTE: "full" polygons severly break connectivity checking, as the code
always treats broken up pieces of the polygon as being connected.
It _might_ have been better to leave this support broken - so
users don't inadvertently create polygons with the "fullpoly" flag.
TODO: Consider removing, hiding or adding warnings to this feature.
| src/action.c | diffblobblamehistory | |
| src/create.c | diffblobblamehistory | |
| src/strflags.c | diffblobblamehistory |