ConvertBrdLayerToPolygonalContours() convert basic graphic items to their
polygonal shapes to allow plotting them in DXF export and vrml export.
For PCB_TABLE, the conversion of PCB_TABLE basic graphic items (textx, segments)
was not made.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/21934
When moving an object in pcbnew, instead of using the constrainer to
restrict motion, we use it to build snapping guidelines that are visible
to the designer and make keeping movement on the various axes easier but
not required
(We have a different "Expand Selection" command now,
and this was never a great name for showing
more choices anyway.)
Also treat tablecells as opaque when guessing
selection candidates. It's unlikely there's anything
under them and keeping to their text bounds feels
counter-intuitive.
A track can be connected to a pad or a via when just crossing or touching it.
So we can create 2 teardrops one from pad/via to track start point and the other
to track end point. However this is acceptable only if the pad/via position is inside
the track. Otherwise the 2 teardrop shapes can be strange (and of course incorrect)
Fixes https://gitlab.com/kicad/code/kicad/-/issues/21851
We need to snap the position to the grid at the start of movement with
the keyboard because it will snap to the movement point of the item when
we are moving, so the difference between mouse position and grid
position will end up being some fractional value that appears random
Fixes https://gitlab.com/kicad/code/kicad/issues/21682
Up/Down flipping needed to be implemented and since it includes a
rotation, we need to specially account for tables in this case to avoid
walking
Fixes https://gitlab.com/kicad/code/kicad/issues/21906
Remove support for point-editing of non-cardinally rotated
barcodes.
Remove support to separately update just the barcode symbol
or just the text.
Removes the point-editor behaviour of using the outside
bounding box. Even when the barcode is inverted, it
sometimes feels like it should be growing/shrinking the
margin, not the barcode. It's more predictable when the
corners are on the symbol.
Angular constraints should have an existing origin to constrain against.
When placing items, this doesn't make sense, so we temporarily disable
the angle snapping
When nothing is selected in the footprint and symbol editors, we show
the properties of the footprint and symbol, allowing easy access to
their properties
A track can be connected to a pad when just crossing it. So we can create 2 teardrops,
one from pad to track start point and the other to track end point.
However this is acceptable only if the pad position is inside the track.
Otherwise the 2 teardrop shapes can be strange (and of course incorrect
Fixes https://gitlab.com/kicad/code/kicad/-/issues/21851
jean-pierre charras
JamesJCode
Seth Hillbrand
Jeff Young
dsa-t