giseldo/neodataset huggingface dataset:
Not sure if a bug: F8 in V5.0 nightly eeSchema on large file crashes KiCad (lp:#1754402)

[Original report](https://bugs.launchpad.net/bugs/1754402) created by **Brian Piccioni (br0an)**
```
I recently read about using F8 to update the PCB from eeSchema. I figured
I'd test it and my last file was

A64-TERES\TERES-PCB1-A64-MAIN_Rev_C\TERES_PCB1-A64-MAIN_Rev.C.pro

I loaded the project, opened eeSchema and PCBNew from Kicad and hit F8. The
system simply hangs (no activity for at least 10 minutes). On other
projects the context switches to PCBNew and a menu pops up quite quickly
after PCBNew has loaded.

I got those files from here
https://github.com/OLIMEX/DIY-LAPTOP/tree/master/HARDWARE/A64-TERES/TERES-
PCB1-A64-MAIN_Rev_C

THIS IS NOT MY PROJECT! I was simply using the files because it is the most
complex KiCad project I have access to and I am stress testing an
application.

I figured I'd report it because often bugs only show up in obscure use
cases. Note that this is the same project associated with this anomaly
https://bugs.launchpad.net/bugs/1750620

Application: kicad
Version: (5.0-dev-4108-g1013f8160), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1
librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```

Story points: 10.0
3d viewer: a poor approximation of big arcs/circles in Edge.Cuts (lp:#1754252)

[Original report](https://bugs.launchpad.net/bugs/1754252) created by **Eldar Khayrullin (eldar)**
```

Application: kicad
Version: 5.0.0-rc2-dev-unknown-8fcbb64~62~ubuntu17.10.1, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0
(+libidn2/2.0.2) librtmp/2.3
Platform: Linux 4.13.0-36-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    Curl: 7.55.1
    Compiler: GCC 7.2.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```
Original tags: 3d-viewer

Story points: 6.0
GerbView: Selection of layer in dropdown list does not actually select the layer (lp:#1754135)

[Original report](https://bugs.launchpad.net/bugs/1754135) created by **Aimylios (aimylios)**
```
After opening a couple of GERBER files in GerbView the active layer can be
selected by clicking on a layer name in the "Visibles" list (a small
triangle appears left to the entry). This will bring the layer in the
foreground, update the format info box and also select it in the dropdown
list in the upper toolbar.

It is also possible to just select a layer in the dropdown list. This will
also bring it in the foreground, but the format info box is not updated and
there is no triangle marking the entry in the "Visibles" list.

This is very confusing. In my opinion, selecting a layer in the dropdown
list should have the same effect as clicking on its name in the "Visibles"
list. At least the format info box at the right side of the dropdown list
should be updated (this is how I discovered this in the first place).

I observe the same behaviour with recent builds of KiCad on both Linux and
Windows. It is GAL-only, as the layer selection logic in the Legacy Toolset
seems to be completely different.


--------------------
Version information:

Application: gerbview
Version: 5.0.0-rc1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.55.1 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.18.0
(+libidn2/2.0.3) libssh2/1.8.0 nghttp2/1.25.0
Platform: Linux 4.15.6-300.fc27.x86_64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.64.0
    Curl: 7.55.1
    Compiler: GCC 7.3.1 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=OFF
```
Original tags: gal gerbview

Story points: 6.0
Eagle import ignores net class and net class settings (lp:#1754130)

[Original report](https://bugs.launchpad.net/bugs/1754130) created by **Jakub Kozdon (fldrivers)**
```
File > Import Project > EAGLE CAD. After that schematic and layout looks
almost same as in Eagle. But after Fill/Refill all zones are filled with
default settings. Also all nets has default net class, so routing tracks
can violate Eagle net class settings. This can create dangerous situations
where clearance for netclass is higher than default.

-----

Application: kicad
Version: (5.0.0-rc2-dev-100-g5a33f09), release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.38.0 OpenSSL/1.0.1t zlib/1.2.8 libidn/1.29 libssh2/1.4.3
librtmp/2.3
Platform: Linux 3.16.0-5-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.55.0
    Curl: 7.38.0
    Compiler: GCC 4.9.2 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=OFF
    KICAD_SPICE=OFF
```
Original tags: eagle import pcbnew

Story points: 10.0
GerbView: Incorrect scaling of EXCELLON drill file (lp:#1754121)

[Original report](https://bugs.launchpad.net/bugs/1754121) created by **Aimylios (aimylios)**
```
This might be a PEBCAK instead of a bug, but I'll report it anyway because
I could not find any information about this specific issue. I can reproduce
it with recent builds of KiCad on both Windows and Linux.

I do have an EXCELLON drill file that was generated with Altium Designer
and has the following file header:
M48
;Layer_Color=9474304
;FILE_FORMAT=2:5
INCH,LZ
;TYPE=PLATED

I can open this file in GerbView, but the scaling is not correct. The size
of the individual drills is OK, but the x and y positions are scaled by a
factor of 10, i.e. if the correct position of a drill is x=0.1in y=0.1in
GerbView shows it at x=1.0in y=1.0in. The corresponding GERBER files do not
have this issue.

Interestingly, the format information in the upper toolbar says "fmt: in
X2.4 Y2.4 no TZ" (see attached screenshot), but it should be X2.5 Y2.5
according to the file header. The GERBER files are correctly identified as
"fmt: in X2.5 Y2.5 no LZ".

Unfortunately I can not share the whole file, but I have extracted a small
part of it that should be sufficient to demonstrate the problem.


--------------------
Version information:

Application: kicad
Version: (5.0.0-rc2-dev-70-g2da7199a3), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1
librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```
Original tags: gerbview

Story points: 6.0
Footprint Name field in Save Footprint dialog does not allow characters 's','p','a','c','e', and 't','b' (lp:#1754120)

[Original report](https://bugs.launchpad.net/bugs/1754120) created by **Dan Green (danngreen)**
```
In Footprint Editor, the "Save Footprint" dialog box does not allow certain
letters in the "Footprint Name" text field.

Interestingly, the disallowed characters exactly match the characters in
the word "space" and in the word "tab": that is, the lower-case letters
's','p','a','c','e', 't', ('a'), 'b' are not allowed

Perhaps it is related to these words ("space" and "tab") being present in
MODULE::StringLibNameInvalidChars(), which appears to be the validator for
this text field.
I would post a patch fix, but am not able to compile at this time.

Note: the Library Filter text field in the same dialog box allows these
characters, just fine.


Version: (5.0.0-rc2-dev-101-gf7ef010), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
Platform: Mac OS X (Darwin 17.4.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.61.0
    Curl: 7.43.0
    Compiler: Clang 7.3.0 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```

Story points: 14.0
GerbView: Aborting "Measure distance between two points" tool enables autopanning (lp:#1754100)

[Original report](https://bugs.launchpad.net/bugs/1754100) created by **Aimylios (aimylios)**
```
Aborting the "Measure distance between two points" tool by pressing ESC
correctly terminates the tool, but leaves the autopanning mode switched on.
I can reproduce this with recent builds of KiCad on both Linux and Windows.

Steps to reproduce:
1. Start GerbView
2. Click on the "Measure distance between two points" tool in the left
toolbar
3. Click somewhere on the canvas to start a measurement (a ruler appears)
4. Press ESC key
5. The "Measure distance between two points" tool is not active anymore (as
expected), but the cursor is still in autopanning mode, which makes it
difficult to move it outside of the canvas


--------------------
Version information:

Application: gerbview
Version: 5.0.0-rc1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.55.1 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.18.0
(+libidn2/2.0.3) libssh2/1.8.0 nghttp2/1.25.0
Platform: Linux 4.15.6-300.fc27.x86_64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.64.0
    Curl: 7.55.1
    Compiler: GCC 7.3.1 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=OFF
```
Original tags: gal gerbview

Story points: 6.0
GerbView: Crash while using "Zoom to selection" tool (lp:#1754094)

[Original report](https://bugs.launchpad.net/bugs/1754094) created by **Aimylios (aimylios)**
```
GerbView crashes when clicking twice on the "Zoom to selection" tool icon
in the upper toolbar. This is a GAL-only problem, the Legacy Toolset is not
affected. I can reproduce it with recent builds of KiCad on Linux as well
as on Windows.


Steps to reproduce:
1. Open GerbView
2. Click on the "Zoom to selection" tool icon in the upper toolbar
3. Click once again on the same "Zoom to selection" tool icon
4. GerbView crashes because of a segmentation fault


--------------------
Version information:

Application: gerbview
Version: 5.0.0-rc1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.55.1 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.18.0
(+libidn2/2.0.3) libssh2/1.8.0 nghttp2/1.25.0
Platform: Linux 4.15.6-300.fc27.x86_64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.64.0
    Curl: 7.55.1
    Compiler: GCC 7.3.1 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=OFF
```
Original tags: gal gerbview

Story points: 6.0
Save footprint dialog doesn't allow input of several alphanumeric characters (lp:#1754083)

[Original report](https://bugs.launchpad.net/bugs/1754083) created by **fierst (fierst)**
```
To Reproduce:

After making a new footprint or editing an existing footprint in the
footprint editor, press the "Save" button or the "Save" menu item in the
File drop-down menu. In the "Footprint Name" field, attempt to type any of
the following characters:

abcepst

The characters can be pasted in manually but not entered directly from the
keyboard. Capital characters (i.e., ABCEPST) all work as expected.

This issue was present in the previous nightly build, albeit with fewer
disallowed characters ("s" and "t" were both previously functional)

Version Information:

Application: kicad
Version: (5.0.0-rc2-dev-107-g49486b83b), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1
librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```

Story points: 6.0
Layer setup can be changed leading to data loss (lp:#1754049)

[Original report](https://bugs.launchpad.net/bugs/1754049) created by **eelik (eelik)**
```
It's possible to change the layer setup, the used layers, so that a layer
which has items is removed. It could be OK but it's potential data loss
because it's done silently without warning. I did it, although I can't
imagine how it happened without me noticing it before several changes and
git commits to a board. Apparently I was trying to remove Adhesive layers
but accidentally clicked F.Paste. Why it didn't give errors before now is a
mystery.

Doing it with F.Paste layer leads to paste-only pads to loose their layer
in the file, for example
(pad "" smd rect (at 0 1 270) (size 1 0.75) (layers F.Paste)
becomes
(pad "" smd rect (at 0 1 270) (size 1 0.75) (layers)

When opening such a board a Warning dialog is shown, for example:
16:27:52: footprint D14, pad (unnamed): could not find valid layer for pad


This data loss happened on Windows about a month ago with a then current
nightly build.
```
Original tags: pcbnew

Story points: 6.0
Feature request: Add "skip overlapping" to "Create array" (for e.g. via stitching) (lp:#1754001)

[Original report](https://bugs.launchpad.net/bugs/1754001) created by **Matthijs Kooijman (matthijskooijman)**
```
Currently, the "Create array" dialog creates an array of elements, even if
that would result in overlapping footprints or other DRC errors. For
creating a grid of stitching via's, it would be useful if any elements that
would overlap with existing tracks, footprints, etc. would simply be
skipped.

I'm not sure what the best definition of "overlapping" would be. At
minimum, it should involve clearance, but a more generic definition might
be "if it would generate a DRC error". Perhaps different kinds of overlap
would suit different usecases.

Adding this option would implement a basic version of
https://bugs.launchpad.net/kicad/+bug/1731763
```

Story points: 14.0
Refilling zone with DRC option "refill all zones" leads to misleading zone display (lp:#1753901)

[Original report](https://bugs.launchpad.net/bugs/1753901) created by **Strntydog (strntydog)**
```
I am using nightly PPA. 5.0 rc2

If you have a zone, and check the DRC option "Refill All Zones before
performing DRC" then the zone is refilled, BUT the old zone outline
displays on the board, not the recalculated one.

DRC Option: http://i.imgur.com/fNnPuG4.png
Example Board.  I placed a GND via over the fill near the SOT23.  Did a DRC
and chose the option to regerate the zone. : http://i.imgur.com/hKfPJ22.png

The DRC succeeded without error, and stated the zone had been refilled.
BUT visually it had not changed.  However, rendering a 3D view shows the
Zone was in fact, actually changed.

Zooming the window or other redraws does not fix the problem.  Refilling
the zones with the "B" key does correctly redraw the zone.

This is highly misleading when editing a board, because the visual
representation of the board is not the actual board layout.

Version:
Application: kicad
Version: 5.0.0-rc2-dev-unknown-2da7199~62~ubuntu17.10.1, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0
(+libidn2/2.0.2) librtmp/2.3
Platform: Linux 4.13.0-32-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    Curl: 7.55.1
    Compiler: GCC 7.2.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```
Original tags: drc pcbnew

Story points: 6.0
copy layer colors between Pcbnew, Modedit and GerbView (lp:#1753789)

[Original report](https://bugs.launchpad.net/bugs/1753789) created by **joost (boerhout)**
```
macos 10.12.16, rMBP
nightly:kicad-20180301-033129.ce1bd4c-c4osx

pcbnew and the footprint editor have their own color settings for layers
and items. The pcbnew preference settings file confirms this with a series
of color settings for each program.

Different colors for the board layout and foot print is confusing i.e. a
change in one should be reflected by the other - this duplicate set up is
annoying and time consuming. Instead, only a single color table should be
referred to in the pcbnew preference file.
```
Original tags: pcbnew

Story points: 14.0
Feature request: CAM settings import (lp:#1753775)

[Original report](https://bugs.launchpad.net/bugs/1753775) created by **Juliean Galak (jgalak)**
```
I believe feature requests go here, under bug reports.  If not, my
apologies, please feel free to
delete.

I've recently come to KiCad from Eagle, and I find myself missing a useful
feature - the ability to have a board manufacturer provide a CAM file that
can be imported by the software to automatically set the the Gerber
generation settings as appropriate to that manufacturer.  A number of PCB
manufacturers provide these files for Eagle and other programs - OSHPark,
SeedStudio, etc.

As far as I can tell there's no such capability in KiCad. I would love to
see it added in a future version.
```
Original tags: pcbnew

Story points: 14.0
pcbnew save & load preferences saves/loads project instead (lp:#1753659)

[Original report](https://bugs.launchpad.net/bugs/1753659) created by **joost (boerhout)**
```
macos 10.12.6, retina macbook pro
nightly: kicad-20180301-033129.ce1bd4c-c4osx

In pcbnew, preferences/save preferences brings up the save project diaglog
instead. Similarly, preferences/load preferences, brings up the load
project diaglog.

It appears impossible to save/load the actual preferences.
```
Original tags: pcbnew

Story points: 6.0
Assert before starting almost any KiCad sub-program (lp:#1753592)

[Original report](https://bugs.launchpad.net/bugs/1753592) created by **Kevin Cozens (qq3dh7wn6set-fehmn-mm0v6n6x10rb)**
```
I just updated my build of KiCad. I started up the main KiCad dialog. When
I click on icon for any of the main programs (except the icons for Import
Bitmap or PCB Calculator) I get an assertion message. I have to click the
Continue button before the program I selected will start. The assertion
message appears every time. You don't need to exit KiCad and restart it to
see the assertion again.

I have attached a copy of the assertion and backtrace as captured by KiCad.

Application: kicad
Version: (5.0.0-rc2-dev-97-g218f66a), debug build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-116-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=OFF
```

Story points: 12.0
wrl exporter fails to export  rounded rectangular pads (lp:#1753552)

[Original report](https://bugs.launchpad.net/bugs/1753552) created by **m (easyw)**
```
Pads of 'roundrect' type are not exported at all... they are rendered
correctly, but excluded in the exporter (tested on latest dev release
12311)
```
Original tags: export pcbnew vrml wrl

Story points: 6.0
wish: add visual indication of locked tracks in pcbnew (lp:#1753448)

[Original report](https://bugs.launchpad.net/bugs/1753448) created by **Jan F (janfisc)**
```
It would be nice to have a visual indication of locked status on top of
traces (either by overlaying symbols or modifying the netname drawing
style).
see attached picture for a photoshopped example.
```
Original tags: pcbnew wishlist

Story points: 22.0
pcbnew: Text rotation angles limited to 0 or 90 again (lp:#1753362)

[Original report](https://bugs.launchpad.net/bugs/1753362) created by **Kevin Cozens (qq3dh7wn6set-fehmn-mm0v6n6x10rb)**
```
While working on a PCB I noticed that about half of the value and reference
text on the board is upside down. When I went to rotate the text I found
the rotation angles were limited to 0 or 90 degrees once again. I was told
that rotation angles greater than 90 are still possible if I change a
setting. However that setting is on a per footprint basis and requires
several steps to make each change. It will be a lot of work to make all the
changes needed on my board with 25 ICs plus all the additional components.
I have some observations and suggestions about this recent change to
pcbnew.

1. File format change
   The addition of a setting to limit rotations means there has been a file
format change which needs to be documented.

2. Change the label in the dialog box for the setting
   In the Footprint Text Properties dialog box the current text reads
"Unlock text orientation". This is misleading. If the text is locked I
should not be able to change its rotation with the R key. A better label
for the setting is "No text rotation limit". I was originally going to
suggest "Limit text rotation" but that would be the opposite value for the
setting.

3. Disable rotation angle choices when text rotation is limited
   In the Footprint Text Properties dialog box the selections for angles >
90 should be disabled when the text rotation limit is in effect.

4. Make the rotation limit setting global rather than per footprint
   I would prefer setting the rotation limit at the project level or as a
Kicad setting (for all current projects and for future ones).
```

Story points: 6.0