giseldo/neodataset huggingface dataset:
KiCad crashes after closing PCBNew if a python script was executed before (lp:#1844880)

[Original report](https://bugs.launchpad.net/bugs/1844880) created by **DDuck007 (dduck007.01)**
```
Running a python-script in PCBNew, e.g. InteractiveHtmlBom
(https://github.com/openscopeproject/InteractiveHtmlBom) or teardrops, ...
Kicad crashes after closing PCBNew. The script is executed properly and
everything looks fine until closing PCBNew. If it is closed all KiCad
windows including the main-window are closed.

Version:

Application: KiCad
Version: (5.99.0-149-g130d52dd8), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.21.0 (+libidn2/2.1.1) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: pcbnew python

Story points: 6.0
Polygon with single point results in parser error (lp:#1844872)

[Original report](https://bugs.launchpad.net/bugs/1844872) created by **Rene Poeschl (poeschlr)**
```
A forum user reported that they had trouble opening a pcb file of theirs on
the next day. The parser complains on a polygon with a single point (line
1240 in the file)

Forum post: https://forum.kicad.info/t/unable-to-load-pcb-file/19022/17
```
Original tags: pcbnew

Story points: 6.0
Setting Canvas Scale to > 1 messes up 3DViewer rotation center

[Original report](https://bugs.launchpad.net/bugs/1844857) created by **Romain (romain145)**
```
KiCAD is displayed in very small characters on High DPI 4k screen.

To have it displayed at a usable scaling, here is the workaround:
Open the app you want to enhance scaling.
Right-click the app in the taskbar.
Right-click the name of the app and select Properties.
Quick Tip: You can also find the app's .exe file, right-click it, and
select Properties.
Click the Compatibility tab.
Under "Settings," check the Override high DPI scaling behavior option.
Under "Scaling performed by" drop-down menu, select System (Enhanced).


Application: KiCad
Version: (5.1.4)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: hidpi windows wxwidgets

Story points: 10.0
Eeschema context menu not working under Cairo (lp:#1844826)

[Original report](https://bugs.launchpad.net/bugs/1844826) created by **Seth Hillbrand (sethh)**
```
Right-click in eeschema should bring up the context menu.  This seems to
happen only intermittently at the moment when using Cairo.  Using OpenGL,
the context menu is consistently and correctly displayed.

This does not seem to affect pcbnew.

Application: Eeschema
Version: (5.99.0-111-gae79a2bdc), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1c zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3
Platform: Linux 4.19.0-5-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    Compiler: GCC 8.3.0 with C++ ABI 1013

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
    KICAD_STDLIB_DEBUG=OFF
    KICAD_STDLIB_LIGHT_DEBUG=OFF
    KICAD_SANITIZE=OFF
```
Original tags: eeschema gal

Story points: 6.0
Via Calculator gives too low resistance values (lp:#1844804)

[Original report](https://bugs.launchpad.net/bugs/1844804) created by **Philipp Legrum (philulm)**
```
I tried the new VIA calcualtor for the first time.
See attached screenshot.

Reconstrucing the formula within Python, my calculation gives the same
mantissa but is x100 off from what KiCAD says.

I hardly dare to report a bug here, because I know from experience how easy
it is to get orders of magnitudes wrong... But KiCad's resistance values
seem so low.

Also, I do not understand what Clearance hole diameter is. The black
circle, I guess. Couldn't that be labeled in the sketch? The PCB Calculator
shows negative capacitance values for improper input.


Application: KiCad
Version: (5.99.0-135-ga1fe8cfa5-dirty), release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2s zlib/1.2.8 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Platform: Linux 4.9.0-3-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.62.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010
Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
    KICAD_STDLIB_DEBUG=OFF
    KICAD_STDLIB_LIGHT_DEBUG=OFF
    KICAD_SANITIZE=OFF
```
Original tags: pcb-calculator

Story points: 8.0
Pads can connect when not touching (lp:#1844727)

[Original report](https://bugs.launchpad.net/bugs/1844727) created by **Seth Hillbrand (sethh)**
```
After the cardinal points connection was added for lp:1840721, rotated pads
can be connected by overlapping cardinal bounding box points (but not pads)
as in the attached file.


Application: KiCad
Version: (5.99.0-145-gb7128639f-dirty), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1c zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3
Platform: Linux 4.19.0-5-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    Compiler: GCC 8.3.0 with C++ ABI 1013

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
    KICAD_STDLIB_DEBUG=OFF
    KICAD_STDLIB_LIGHT_DEBUG=OFF
    KICAD_SANITIZE=OFF
```
Original tags: pcbnew

Story points: 6.0
Eeschema - option to use also .mod files as a simulation model (lp:#1844718)

[Original report](https://bugs.launchpad.net/bugs/1844718) created by **Jakub Kozdon (fldrivers)**
```
Many manufacturers provide their models as .mod file. It will be beneficial
if default file selector can use .mod files in parallel with .lib files.
Now there are two more clicks needed.

--

Application: KiCad
Version: (5.99.0-111-gae79a2bdc), debug build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2s zlib/1.2.8 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Platform: Linux 4.9.0-9-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.62.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
    KICAD_STDLIB_DEBUG=OFF
    KICAD_STDLIB_LIGHT_DEBUG=OFF
    KICAD_SANITIZE=OFF
```
Original tags: eeschema ngspice starter

Story points: 6.0
"change type" sometimes flips direction of label (lp:#1844716)

[Original report](https://bugs.launchpad.net/bugs/1844716) created by **David Bridgham (dab-1)**
```
In eeschema if I click right on a local label, select 'Change Type' and
'Change to Hierarchical Label', the result is flipped left to right or
right to left.  Same with changing to a Global Label or back from either.
Changing from local label to text or back does not flip the direction nor
between global label and hierarchical label.

I'm using KiCad 5.1.4 on Debian Linux, full version information is below.

Application: Eeschema
Version: 5.1.4+dfsg1-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 libidn2/2.2.0 libpsl/0.20.2
(+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.39.2 librtmp/2.3
Platform: Linux 5.2.0-2-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.65.1
    Compiler: Clang 7.0.1 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 6.0
Not connecting when label have "_" (lp:#1844683)

[Original report](https://bugs.launchpad.net/bugs/1844683) created by **Hildo Guillardi Júnior (hildogjr)**
```
I am using the last Nightly and some time ago I haven't this issue. Now,
some wire that I label with the "_" character in the name get no connection
in the PCB.

I am sending a project to reproduce it. The by the "UART_RX" label.

Application: KiCad
Version: 5.99.0-unknown-16f4958~86~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-161-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
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema pcbnew

Story points: 6.0
Connecting pads by ones origin inside the second one don't work. (lp:#1844661)

[Original report](https://bugs.launchpad.net/bugs/1844661) created by **Piotr Gałka (piotrgalka)**
```
From https://bugs.launchpad.net/kicad/+bug/1843993 message #3 I understood
that smd offsets were introduced to allow connecting two pads by
positioning origin of one of them inside the second one.
That doesn't work in 5.1.4 stable.
The KEY10.kicad_mod (attached) is designed that way. Top pad1 I left
without offset, but all others smd pads use offsets to have their origin in
top pad1, or pad already connected that way with top pad1.
When I put that footprint at PCB (project attached) I see pads not being
connected and connection lines pointing the pad graphic centers and not
their origins.
Compare KEY_1.png and KEY_2.png. When I connect track to right pad 1 origin
two connection lines disappear. At first I supposed that at that moment
they were found to be connected (thanks to my offsets) but now I think that
both of them are found to be connected to track so they are connected also.

I supposed connection lines would point to pad origins. And I think it
should work that way (if not then what for are the offsets in smd pads).
But what if someone use both X and Y offset and position origin out of pad.
First thought is to not allow it in footprint editor. But in my footprint
would't it be logical to position all pad 2 origins in center of through-
hole pad 2 making them being connected and at once making the connection
line to point where the connection is expected to be done.

Application: KiCad
Version: (5.1.4)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: pcbnew

Story points: 6.0
eeschema: "highlight wires and pins of a net" on /<NO NET> highlights different nets (lp:#1844624)

[Original report](https://bugs.launchpad.net/bugs/1844624) created by **Dino Ghilardi (dino-ghilardi)**
```
On Master branch,
 When different nets have not been named yet (as when a schematic has not
been annotated and the nets have not been named), using the highlight tool
can give wrong result: different nets have the same name (/<NO NET>) and
they are highlighted even if they are not connected.

Since "no information" is better than "wrong information", a simple
solution could be to not highlight the wires if the net name is "/<NO NET>"
(and issue a warning).

To reproduce:
1) Open a generic schematic (without net labels)
2) Clear annotation
3) Highlight a net: all nets get highlighted since all net names are "/<NO
NET>"

In stable version 5.1.4 there is not this behaviour: it seems the nets are
always named (Something like Net-(R?1753720092-Pad2)) even if the schematic
has not been annotated, so there is no risk to see different un-connected
nets highlighted at the same time..

Cheers,
Dino.

-------------------------
Application: Eeschema
Version: (5.99.0-139-gbb596ebda-dirty), release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2s zlib/1.2.8 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Platform: Linux 4.9.0-8-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.69.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 6.0
eeschema undo: missing junctions when undoing delete. (lp:#1844620)

[Original report](https://bugs.launchpad.net/bugs/1844620) created by **Dino Ghilardi (dino-ghilardi)**
```
Undo in eeschema (master branch) does not always work correctly.

To reproduce:
1) Select a block with some junctions.
2) Delete it (del key)
3) undo (ctrl-z).
   The un-done deleted part now does not have some of the junction symbols.

Attached there is a simple project to show the behaviour.

(See the attached images for the before-after the delete+undo operation).

Dragging the wires make the junctions on the dragged part re-appear, so it
seems that the wire is connected but without the junction symbol.

I also had a (probably) related issue on undoing operations on much more
complex schematics, where also bus segments appear like they were copied
from somewhere else, but that is quite erratic and I did not find (yet) a
way to reproduce that in a deterministic (and simple) way.


Note: Stable version 5.1.4 works correctly.

Cheers, Dino.

------------------------------
Application: Eeschema
Version: (5.99.0-139-gbb596ebda-dirty), release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2s zlib/1.2.8 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Platform: Linux 4.9.0-8-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.69.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 6.0
Pcbnew: Tabs in netclass properties Dialog dont stay opened (lp:#1844566)

[Original report](https://bugs.launchpad.net/bugs/1844566) created by **Nikolaus Trnka (dasniggl)**
```
In Pcbnew in the netclass properties Dialog, both of the tabs "filter
netclasses" and "new netclass" open when I click on them with the Mouse
Pointer. But after they opened, they immediatly close. So the only way to
select a netclass, is to click a second time really fast - needs a few
tries to hit it.

- Open a new project
- Open Pcbnew
- Open the Board Properties Dialog, change to the tab Netclasses
- Define a new netclass
- Click on one of the tabs "filter netclass" or "new netclass" (assign
netclass)
-> Both tabs close immediately


Application: Pcbnew
Version: (5.1.4)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: pcbnew ui

Story points: 6.0
eeschema editing fields shows wx error (lp:#1844545)

[Original report](https://bugs.launchpad.net/bugs/1844545) created by **Jonatan Liljedahl (kymatica)**
```
Tap 'e' on a symbol, edit any of the fields, click OK. The attached error
dialog is shown.

Application: Eeschema
Version: (5.1.4-82-gcb0764a9a), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.6.5 zlib/1.2.11 nghttp2/1.24.1
Platform: Mac OS X (Darwin 18.5.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (wchar_t,STL containers,compatible with 2.8)
    Boost: 1.69.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.54.0
    Compiler: Clang 9.0.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_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 6.0
CVPCB window prefs don't save (lp:#1844457)

[Original report](https://bugs.launchpad.net/bugs/1844457) created by **ocb-hd-ccb (ocb-hd-ccb)**
```
I organize different windows to different parts of my screen. Every time I
open a kicad program it opens to where I last had it...EXCEPT for CVPCB.
Several nightlies ago this was not an issue so something changed recently.

Macos Nightly 190916

```
Application: KiCad
Version: (5.99.0-132-g961fbf5f5), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.6.5 zlib/1.2.11 nghttp2/1.24.1
Platform: Mac OS X (Darwin 18.7.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (wchar_t,STL containers,compatible with 2.8)
    Boost: 1.69.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.54.0
    Compiler: Clang 9.0.0 with C++ ABI 1002

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
    KICAD_STDLIB_DEBUG=OFF
    KICAD_STDLIB_LIGHT_DEBUG=OFF
    KICAD_SANITIZE=OFF
```
```
Original tags: cvpcb eeschema ui

Story points: 6.0