giseldo/neodataset huggingface dataset:
Interactive router in Shove mode creates non-45deg tracks which violate DRC (lp:#1810935)

[Original report](https://bugs.launchpad.net/bugs/1810935) created by **eelik (eelik)**
```
This is a bit difficult to describe (and search for) so I don't know if
this is a duplicate. But here is a video of a situation into which I bump
every now and then with the interactive router in Shove mode.

The router suddenly finds a route which violates DRC and the angle of the
track isn't n*45deg even though I have limited the angle. It kind of takes
a shortcut, the shortest distance between points A and B. I can't find the
reason or exact situation when this happens, it just happens every now and
then. It has happened for a long time, it doesn't depend on some specific
version. IIRC I have seen this even long before 5.0.

Here are some restrictions which I think apply for the situation:

I have used or am using small grid, e.g. 0.05mm in this specific case.
Maybe I have used even smaller for the same project and then changed. It
probably happens when I try to route to a pad, or work nearby a pad, but
I'm not sure about this. The distance is pretty small, a couple of mm at
most (again IIRC).



Application: kicad
Version: (6.0.0-rc1-dev-1491-g0a4812be0), 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: 16.0
Simulations PNG export has black font for legend on black background (lp:#1810914)

[Original report](https://bugs.launchpad.net/bugs/1810914) created by **Karl Zeilhofer (zeilhofer)**
```
Exported PNG attached.



Application: kicad
Version: 5.0.2-bee76a0~70~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.59.0 mbedTLS/2.8.0 zlib/1.2.11
Platform: Linux 4.15.0-38-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_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema export ngspice

Story points: 10.0
KiCAD crashes on MacOS Mojave Eeschama/libedit (lp:#1810906)

[Original report](https://bugs.launchpad.net/bugs/1810906) created by **Franz Baureis (fb83)**
```
After creating a new symbol in the "Transistor_BJT" or a newly created
library and saving it any editing leads to a crash of the Symbol library
editor and KiCAD.

To reproduce the bug:

1. Open the Symbol library editor either from KiCAD or Eeschema
2. Create a new library or use an existing one (e.g. "Transistor_BJT")
3. Create a new part (e.g. Named "DMMT3904W", Numbers of Units per Package
does not matter)
4. Save the newly created part.
5. Editing this Part leads to an immediate crash

System Info:

MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports)
OS:           macOS Mojave Version 10.14.2
Processor:    2,3 GHz Intel Core i5
RAM:          16GB 2133MHz LPDDR3
Graphic Card: Intel Iris Plus Graphics 655 1536MB


Version Info:

Application: kicad
Version: (5.0.2-4-g3082e92af), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.6.4 zlib/1.2.11 nghttp2/1.24.1
Platform: Mac OS X (Darwin 18.2.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.68.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_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: macos

Story points: 40.0
pcbnew modifies unchanged footprints when saving (lp:#1810870)

[Original report](https://bugs.launchpad.net/bugs/1810870) created by **Seth Hillbrand (sethh)**
```
When opening an existing kicad_pcb file, kicad will update the footprints
in the board, changing coordinates for multiple items and save the changes.
I think that this may be problematic

Steps to reproduce:
1) clone Alexis' motherboard repository[1]
2) Open motherboard.kicad_pcb
3) Make a change and then undo the change so that the board is nominally
un-changed but the save button activates
4) Save the board
5) Run git diff on motherboard.kicad_pcb

There are a number of changes as the file is dated although the file
version is the same.

A) Pads change coordinates from -0.35 to 0.349999
B) All fp_poly sections change substantially, including removing
coordinates

While the files do not appear corrupted, I think we shouldn't modify the
footprint coordinates and definitely not remove points unless the user
specifically makes that change.

[1] https://github.com/c4puter/motherboard
```

Story points: 10.0
Wishlist: DRC report should display the violation measurement (lp:#1810845)

[Original report](https://bugs.launchpad.net/bugs/1810845) created by **Robert (robee)**
```
The DRC reports show us each error with good information about which 2
elements are in violation, but it would be even better to report the actual
measurements that DRC is seeing.  So if I have 4 mil spacing rules and I
see a 3.98 mil spacing, I know I can ignore it.  This also allows me to set
more restrictive rules to see if I can make changes that would aid
manufacturing or lower the cost.  Finally, I'm one who believes tools can
be wrong, so I'd like to verify that the measurement the tool is seeing is
something that is really a problem.  Knowing the tool calculation will tell
me if DRC is off.
```

Story points: 10.0
Pcbnew: Pan after cursor warp (lp:#1810787)

[Original report](https://bugs.launchpad.net/bugs/1810787) created by **Fabián Inostroza (fabianinostroza)**
```
After some actions the cursor is warp to the border of the canvas and if
"pan while moving object" is enabled then canvas start panning (sometimes
very fast). I doubt this is what one would expect, at least in the cases
shown in the attached video.

Application: kicad
Version: (6.0.0-rc1-dev-1493-g2d6f8a97b-dirty), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.62.0 GnuTLS/3.6.5 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.35.1 librtmp/2.3
Platform: Linux 4.19.0-1-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.62.0
    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=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=OFF
```
Original tags: pcbnew

Story points: 6.0
Aliases deletion Error in Symbol Editor (lp:#1810768)

[Original report](https://bugs.launchpad.net/bugs/1810768) created by **Piotr Gałka (piotrgalka)**
```
Windows nigtly form 1.1.2019
In Symbol Editor deleting aliases deletes not the intended ones and then
KiCad at symbol tree showes aliases before deletion (even after reopening
KiCad) but symbol properties window showes only one and not the one I left.

Screenshots in zip:
01 - Exporting Symbol R1005 to new lib: Test.lib
02 - Aliasys list of that symbol in Test.lib
03 - after deleting (using basket symbol) all aliases except 10k
04 - after closing (with OK) Symbol Properties window it showes that only
47 alias was changed (to be saved)
05 - after Ctrl+S
06 - after [-] and [+] at Test lib and opening Symbol Properties
07 - after reopening Symbol Editor
If I close the whole KiCad and then open it and open Symbol Editor I have
the same situation - at tree I see 5 aliases, and in Symbol Properties only
one and not the one I left (I left 10k, but 47 was left)

I bagan to make these screenshots because I get some Error window during
manipulation in aliases list. While trying to repeat it I got into what I
described here. But there is also some other bug. Don't know if I will find
it once more.


Application: kicad
Version: (6.0.0-rc1-dev-1455-g4b7ef22ec), 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
```

Story points: 10.0
eeschema crashes on OSX 10.14.2 (lp:#1810744)

[Original report](https://bugs.launchpad.net/bugs/1810744) created by **hedefalk (hedefalk)**
```
Since upgrading to OSX Mojave (I think it worked better before) I have a
lot of crashes in eeschema. It happens when doing add component, basically
every second time or so I try to add something so very hard to do schematic
capture right now. I first had the issue in 5.0-something nightly but the
problem persists after upgrading to 5.0.2 release build:


Application: kicad
Version: (5.0.2-4-g3082e92af), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.6.4 zlib/1.2.11 nghttp2/1.24.1
Platform: Mac OS X (Darwin 18.2.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.68.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_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

I'll attach OSX crash thread dump.
```
Original tags: osx

Story points: 6.0
Wrong sync canvas-mouse when using keyboard arrows (lp:#1810684)

[Original report](https://bugs.launchpad.net/bugs/1810684) created by **Hildo Guillardi Júnior (hildogjr)**
```
Sometimes I use the arrows on keyboard to move/access some component in
Eeschema/Pcbnew. But the canvas loss the synchronization after some use.

The video attached shows better:
In the begging I press `m` to move a connector, the part in the canvas and
the mouse are not synchronized anymore.
I move the move the mouse and every thing became OK.
At the end I try to edit a sequence of labels. Check that the last one
picked is not that one the the mouse was pointing (this happens every time
that I use the keyboard arrows).




My KiCad:

Application: kicad
Version: 6.0.0-rc1-unknown-4493af9~66~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-141-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=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
```
Original tags: eeschema

Story points: 6.0
disambiguation menu not showing in track placement mode (lp:#1810611)

[Original report](https://bugs.launchpad.net/bugs/1810611) created by **Sergey A. Borshch (sb-sf)**
```
Steps to reproduce:
1) choose some track under footprint or somewhere where clarification
dialog displayed selecting this track.
2) Select track placement tool
3) move mouse cursor over track, press Del or backspace hotkey. Nothing
happens.
4) cancel track placement tool, clarification menu appears.

Version info: today's git head,
Application: pcbnew
Version: (6.0.0-rc1-dev-1481-g5e70534-dirty), release build
Libraries:
    wxWidgets 3.0.2
Platform: Linux 4.4.0-138-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
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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=OFF
    KICAD_USE_OCE=OFF
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: gal

Story points: 6.0
Footprint Properties: Show Cartesian axes in 3d preview with sizing (lp:#1810596)

[Original report](https://bugs.launchpad.net/bugs/1810596) created by **Michele Giorato (mr-miky64)**
```
I think one of the most boring things is the absence of the representation
of the Cartesian axes.
Often, indeed almost always, when you have to connect a 3D object to a
footprint, a lot of problems arise with the positioning, especially if the
purpose is to modify the object so that it does not need to offset the
footprint.
Problems arise, in my opinion, from the absence of a representation of the
Cartesian axes and the fact that the footprint is displayed without
ignoring the rotations applied during placement on the pcb.
The thing that puzzles me is that if you turn the component on the pcb and
then edit the 3D properties, the graphic representation is strongly
misleading because the x and y movements are exchanged.
I think it would be more correct to represent the 3d object on the
footprint without any rotations applied to the pcb or as represented in the
footprint editor.


Application: kicad
Version: 6.0.0-rc1-unknown-r14713-3a3bbbb5, debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 zlib/1.2.11 brotli/1.0.5 libidn2/2.0.5
libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.8.5/openssl/zlib nghttp2/1.34.0
Platform: Linux 4.19.13-300.fc29.x86_64 x86_64, 64 bit, Little endian,
wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.66.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.1 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=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=OFF
```
Original tags: 3d-viewer

Story points: 14.0
Symbol properties dialog - can't exit Fields grid using keyboard (lp:#1810569)

[Original report](https://bugs.launchpad.net/bugs/1810569) created by **Ben Gamari (bgamari)**
```
Currently (as of 5.0.1) the schematic editor's symbol properties dialog
essential requires the use of the mouse. There is no reason why this should
be the case: most programs assign keystrokes to UI elements accessible with
combinations of Alt and letter keys which when pressed give focus to the
element.
```
Original tags: eeschema ui

Story points: 18.0
macOS - Crash on activating 3d view (lp:#1810550)

[Original report](https://bugs.launchpad.net/bugs/1810550) created by **John Pateman (gasman2016)**
```
On opening the 3D view from either pcbnew or the footprint viewer, the
whole application crashes. This was not the observed behaviour with either
5.0.1 or with a current nightly - both of which show the 3D view correctly.
I have attached the stack trace.

iMac 27" 3.06 GHz Intel Core 2 Duo
12 GB 1067 MHz DDR3
ATI Radeon HD 4670 256 MB
macOS 10.13

Application: kicad
Version: (5.0.2-4-gb601aea34), 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.7.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.51.0
    Compiler: Clang 8.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_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: macos

Story points: 8.0
schema: zoom with scroll wheel zooms of center (lp:#1810403)

[Original report](https://bugs.launchpad.net/bugs/1810403) created by **Nicholas Savenlid (nicholas-z)**
```
Zooming with the scroll wheel no longer works as before.

Used to zoom into where you had the cursor.

Now it zooms into center of page ?

Application: kicad
Version: (6.0.0-rc1-dev-1459-g5c055f3f8), 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
```

Story points: 10.0
PCBNew - stange rats nest behavior  (lp:#1810312)

[Original report](https://bugs.launchpad.net/bugs/1810312) created by **Art (diametrix)**
```
Lately I noticed that rats nest lines don't always disappear when you make
track connections and sometimes they lead to empty places on the board.  It
usually happens during routing and then if your restart PCBNew those false
rats nest lines go away.  I was able to capture a video of such anomaly.

If you hide board's rat's nest those anomalies are still showing.




Application: kicad
Version: (6.0.0-rc1-dev-1448-g26a337db1), 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
spice plot is stepped (lp:#1810311)

[Original report](https://bugs.launchpad.net/bugs/1810311) created by **Thomas Pointhuber (pointhi)**
```
# HowTo Reproduce

1. draw simple voltage divider
2. simulate with DC Source, 0V-10V, 100m voltage steps
3. see that no interpolation takes place in the graph

# Expected behavior

interpolate results at least in a linear way

# Version Information

Application: kicad
Version: (6.0.0-rc1-dev-1447-gdeae6d5bb), debug build
Libraries:
    wxWidgets 3.1.1
    libcurl/7.63.0 OpenSSL/1.1.1a zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.35.1
Platform: Linux 4.19.12-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.1.1 (wchar_t,wx containers) GTK+ 3.24
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.62.0
    Compiler: Clang 7.0.1 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    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 ngspice

Story points: 6.0
Auto-place is Tool not Place (lp:#1810301)

[Original report](https://bugs.launchpad.net/bugs/1810301) created by **Piotr Gałka (piotrgalka)**
```
0 of work, only decision needed. Would be good before 5.1 I think.

I am sure in PcbNew the menu "Auto-place" should be rather located in
"Tools" menu.

In English "Auto-place" seems to fit to "Place". But in Polish menu "Place"
is translated to "Add" and I would not look for "Auto-place" there.
Translation is good - the problem is that Auto-pace is really an automatic
tool and not placing (adding) one element by user like other positions in
Place menu.

I would also consider if:
"Change Footprints...",
"Swap Layers...",
"Cleanup Tracks and Vias..."
are not enough clever to promote them to Tools menu.
I have not used these functions ever so I have no opinion - only suggestion
to consider.

Also from Polish menu I would think of moveing "Set Layer Pair..." from
"Tools" to "Settings". But as "Settings" in English are _only_
"Preferenses" I don't courage to suggest it.
But in my opinion the better name for Preferences would be Settings and
then....

I don't know how other translations. But may be in other languages also
Preferenses are translated to Settings and Place to Add.

I think my suggestions goes towards more universal (fit to many
translations) menu organisation.
```
Original tags: ui

Story points: 10.0