giseldo/neodataset huggingface dataset:
two wire ends behave differently in eeschema (lp:#1830007)

[Original report](https://bugs.launchpad.net/bugs/1830007) created by **eelik (eelik)**
```
Wires in eeshcema seem to have start and end point. If I press G on one end
the cursor may move to another end. That makes for example dragging from
certain points impossible. It should always grab the nearest point. Wires
shouldn't have any observable direction.

Application: Eeschema
Version: (5.1.0-637-gaee1fe45f), 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: eeschema

Story points: 14.0
Can't maximise "Board Setup" and "Edit Symbol Fields" dialogs. (lp:#1829950)

[Original report](https://bugs.launchpad.net/bugs/1829950) created by **Leandro Heck (leoheck)**
```
The "Board Setup" window is not a fully working window this annoys so much.
Assign net classes, for example, is not a good thing to do on a small
window.

The same happens with "Symbol Fields" window which is a spreadsheet window
that cannot be maximized. It is the best feature on Eeschema but it is
horrible to use since I cant maximize and I can't use the half-screen
shortcuts that came with gnome.

I can't maximize it, just resize with the mouse. I can't move it from the
center of the main window since I am using it on Gnome 3.




Application: kicad
Version: 5.1.2-f72e74a~84~ubuntu19.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1b zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.5) libssh/0.8.6/openssl/zlib nghttp2/1.36.0 librtmp/2.3
Platform: Linux 5.0.0-15-generic 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:
    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 pcbnew ui

Story points: 10.0
eeschema - unfold from bus: double labels in popup menu (lp:#1829878)

[Original report](https://bugs.launchpad.net/bugs/1829878) created by **Dino Ghilardi (dino-ghilardi)**
```
Using the "unfold from bus" right-clicking on a bus lists twice the bus
member names.
Doing it with the shortcut "C" works correctly.

To reproduce the behaviour:
-Define a bus with bus->tools definitions and define
-Draw a bus on the schematic
-Put the name on the bus with "add a net label"
-right-click on the bus and choose "Unfold from bus"
--> probably now you will see "bus has no connections", but this is another
bug: to workaround it, if the label is still black, drag the bus under the
label, than it becomes blue and the bus name is set.


In the menu where to choose the net every bus member is reported twice

Also when the menu reports twice "bus has no connections" the second is
selectable and unfolds a net with name "bus has no connections".

-------------------------------
Tested on commit d3dc7ade8ac8c59c14c457997893032bd15f3b9b

---------------------------------------------------
Application: Eeschema
Version: (5.1.0-636-gd3dc7ade8), debug build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2r 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:
    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: eeschema

Story points: 6.0
Coursor invisible if background white (lp:#1829850)

[Original report](https://bugs.launchpad.net/bugs/1829850) created by **Piotr Gałka (piotrgalka)**
```
I'm used to work with PCB with white background, and wonted to use KiCad in
'my' colours. When I've changed background colour to white the coursor is
still visible, but when I try to place a line (in footprint editor) or
place a track in PCB editor coursor disapears. I believe there is no place
where I can set coursor colour.
The same problem is with Measure distance tool.

I think if coursor colour can't be set by user then not automatically
adapting its colour to background (at least to two oposities - back and
white) is a bug. This is not connected with any user interface change so I
think can be done in V5.


Application: kicad
Version: (5.1.2)-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
Nightly r13127 Menue artifact (lp:#1829817)

[Original report](https://bugs.launchpad.net/bugs/1829817) created by **Sebastian Kulik (sebastiankulik1)**
```
Hi guys,
in latest nightly on Win10x64 "Edit", "View"  and "Place" have very strange
artifact: once clicked on one of them they blinks a while if you going with
mouse just over (without clicking something).
Any iodea?
BEst regards,
Sebastian
Application: KiCad
Version: (5.1.0-627-gbc52f0a03), 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: eeschema ui

Story points: 6.0
Nightly r13127 PCBNew crashes 3-D viewer (lp:#1829815)

[Original report](https://bugs.launchpad.net/bugs/1829815) created by **Sebastian Kulik (sebastiankulik1)**
```
Hi guys,

tested right now latest nightly on Win10x64. Trying to start 3-D viewer
will crash whole KiCAD.
Any ideas?
Best regards,
Sebastian

Application: KiCad
Version: (5.1.0-627-gbc52f0a03), 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
```

Story points: 6.0
MinHoleToHole cannot be R/W using pcbnew.py (lp:#1829804)

[Original report](https://bugs.launchpad.net/bugs/1829804) created by **Dave Vandenbout (devb)**
```
Summary: MinHoleToHole setting in .pro file cannot be read or written using
pcbnew.py

Application: kicad
Version: (5.1.2)-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


Reproduction of bug:

Python 2.7.15 (default, Oct 11 2018, 12:09:51)  [GCC 8.2.0 64 bit (AMD64)]
on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> from pcbnew import *
>>> brd = LoadBoard('test_dr.kicad_pcb')
>>> drs = brd.GetDesignSettings()
>>> drs.m_HoleToHoleMin
37845792  <== I don't know where this value comes from.
>>> drs.SetMinHoleSeparation(12345678)
>>> drs.m_HoleToHoleMin
12345678  <== New hole-to-hole setting.
>>> brd.SetDesignSettings(drs)
>>> brd.Save('test_dr.kicad_pcb')  <== Save updated board.
True
>>> brd = LoadBoard('test_dr.kicad_pcb')  <== Reload updated board.
>>> drs = brd.GetDesignSettings()
>>> drs.m_HoleToHoleMin
0         <== Updated hole-to-hole setting has been lost.
>>>

This same problem affects m_RequireCourtyards and
m_ProhibitOverlappingCourtyards.
The only commonality I can see is that none of these member variables have
the drs.Get*()
methods (e.g. drs.GetMinHoleSeparation()).
```
Original tags: pcbnew python starter

Story points: 6.0
3D view crash Pcbnew (lp:#1829800)

[Original report](https://bugs.launchpad.net/bugs/1829800) created by **Hildo Guillardi Júnior (hildogjr)**
```
3D view freeze Pcbnew to crash. This bug appeared one day after some update
to the Raytracing that made it calculate from the center.



Application: Pcbnew
Version: 6.0.0-unknown-f21face~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.15.0-50-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:
    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: 3d-viewer

Story points: 6.0
Nightly : PCBNEW Continuous reports of exceptions caused by the view menu (lp:#1829780)

[Original report](https://bugs.launchpad.net/bugs/1829780) created by **Michele Giorato (mr-miky64)**
```
Continuous reports of exceptions caused by the view menu.

At the start of pcbnew an requester that signals the thing immediately
opens.
If you choose continue (several times) you enter the pcbnew main screen and
you can use it but only if you don't try to open the view menu.
If you go over the view menu, all the requester reappear and sometimes
everything freezes.

ASSERT INFO:
../src/gtk/menu.cpp(729): assert "Assert failure" failed in SetBitmap():
only normal menu items can have bitmaps

BACKTRACE:
[1] wxMenuItem::SetBitmap(wxBitmap const&)
[2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&)
[3] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[4] wxEvtHandler::TryHereOnly(wxEvent&)
[5] wxEvtHandler::ProcessEventLocally(wxEvent&)
[6] wxEvtHandler::ProcessEvent(wxEvent&)
[7] wxEvtHandler::ProcessPendingEvents()
[8] wxAppConsoleBase::ProcessPendingEvents()
[9] wxApp::DoIdle()
[10] g_main_context_dispatch
[11] g_main_loop_run
[12] gtk_main
[13] wxGUIEventLoop::DoRun()
[14] wxEventLoopBase::Run()
[15] wxAppConsoleBase::MainLoop()
[16] wxEntry(int&, wchar_t**)
[17] __libc_start_main
[18] _start





Application: Pcbnew
Version: 6.0.0-unknown-r15732-813de6a1, debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1b zlib/1.2.11 brotli/1.0.7 libidn2/2.1.1
libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.8.7/openssl/zlib nghttp2/1.38.0
Platform: Linux 5.0.16-300.fc30.x86_64 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.69.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    Compiler: GCC 9.1.1 with C++ ABI 1013

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: pcbnew

Story points: 10.0
eeschema: "unfold from bus" not working (lp:#1829759)

[Original report](https://bugs.launchpad.net/bugs/1829759) created by **Dino Ghilardi (dino-ghilardi)**
```
Right clicking on "bus unfolding" shows the correct menues, but it does not
unfold the signal (no bus entry/wire/label created).

Checked on commit: dbc40096db46c32ffe8f73377e831c6ca08ceab7


---------------------------------------------------------------------
Application: Eeschema
Version: (5.1.0-620-gd701637ea), debug build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2r 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:
    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: bus eeschema

Story points: 6.0
Eeschema: missing convert text type context menu (lp:#1829748)

[Original report](https://bugs.launchpad.net/bugs/1829748) created by **Wayne Stambaugh (stambaughw)**
```
It looks like the convert schematic text to a label type submenu has not
been implemented in the new tool framework.  This includes the following
command IDs: ID_POPUP_SCH_CHANGE_TYPE_TEXT_TO_LABEL,
ID_POPUP_SCH_CHANGE_TYPE_TEXT_TO_HLABEL,
ID_POPUP_SCH_CHANGE_TYPE_TEXT_TO_GLABEL, and ID_POPUP_SCH_CHANGE_TYPE_TEXT.

Application: Eeschema
Version: (5.1.0-620-gd701637ea), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1b 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.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    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
Assert then crash on quit (lp:#1829741)

[Original report](https://bugs.launchpad.net/bugs/1829741) created by **Michael Kavanagh (michaelkavanagh)**
```
Application: Eeschema
Version: (5.1.0-610-g813de6a1f), 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 10.0.1 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=OFF
    KICAD_SCRIPTING_MODULES=OFF
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 6.0
Eagle import: footprint field position not saved correctly (lp:#1829727)

[Original report](https://bugs.launchpad.net/bugs/1829727) created by **Rene Poeschl (poeschlr)**
```
Importing from eagle seems to transfer the footprint field (example
reference) positions correctly. Saving, closing and reopening the pcb will
however result in all positions being reset to how they are defined in the
eagle footprint.

The strange thing is that if one opens the field properties of such a
reference then it is saved correctly.

---

eagle 9.3.2

Application: kicad
Version: (5.1.2)-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: eagle import pcbnew

Story points: 6.0
Eagle import: pcb text justification imported wrongly (lp:#1829711)

[Original report](https://bugs.launchpad.net/bugs/1829711) created by **Rene Poeschl (poeschlr)**
```
The eagle import changes center aligned to right aligned for text fields on
the pcb.

eagle 9.3.2

Application: kicad
Version: (5.1.2)-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: eagle import pcbnew

Story points: 6.0
Eagle import: milling layer is converted to edge cuts layer (lp:#1829708)

[Original report](https://bugs.launchpad.net/bugs/1829708) created by **Rene Poeschl (poeschlr)**
```
The milling layer defines where the milling tool should remove material.
(The centerline defines the toolpath and the width defines the diameter of
the cutter)

The center of lines on the edgecuts layer in kicad (as far as i understand
it) defines the resulting nominal border of the board. (The cutter is
offset from it by half its diameter)

Right now kicad converts lines on the milling layer directly to edge cuts
lines. If my interpretation of the edge cuts layer is correct then the
lines should be converted to two lines and arcs at the end such that the
cutout is defined properly. Or a new layer must be introduced that does the
same as the milling layer in eagle.

Edit: If the edge cuts layer can double as the milling layer (if my
understanding of it is incorrect) then the line width of features on the
milling layer would need to be used for resulting features on the edge cuts
layer. (Right now the edge cuts lines get the default width)

---

eagle 9.3.2

Application: kicad
Version: (5.1.2)-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: eagle import pcbnew

Story points: 6.0