giseldo/neodataset huggingface dataset:
wxpython incompability in Arch Linux (lp:#1747677)

[Original report](https://bugs.launchpad.net/bugs/1747677) created by **ildus (k-dus)**
```
Application: kicad
Version: (2018-02-06 revision e0f7958db)-master, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1
(+libidn2/2.0.4) nghttp2/1.29.0
Platform: Linux 4.14.15-1-ARCH 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.66.0
    Curl: 7.58.0
    Compiler: GCC 7.2.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=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON

If i open 'Browse footprints' in Symbol Properties, then the application
freezes. Same happens if I open 'Assign footprint'.
```

Story points: 6.0
Edit Environment variable: lower-case letters not visible (lp:#1747653)

[Original report](https://bugs.launchpad.net/bugs/1747653) created by **simski (simski)**
```
inpact: confusing.

when starting to type the name of the variable, no typing is visible/no
reaction from interface. only when caps are used type is visible.

suggestion: show wrong chars in red. No visible feedback is confusing. or
translate to caps automatically, ignoring spaces and other wrong chars

kicad nightly:

Application: kicad
Version: no-vcs-found-fe62760~61~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.13.0-32-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=ON
```

Story points: 6.0
Use "Symbol Chooser" in "Edit Symbol Library References" dialog instead of "Symbol Library Browser" (lp:#1747599)

[Original report](https://bugs.launchpad.net/bugs/1747599) created by **Antonio Vázquez Blanco (antoniovazquezblanco)**
```
I have been working in KiCad v4 with the new library repos for a while. I
decided to test the nighlies and found that schematic conversion does not
really work very well.

After some work remapping components one by one someone told me that there
is a hidden functionality in the 'Edit -> Edit Symbol Library Link' menu.
It is nice as a backup when remap does not work properly but it is not very
easy to find.

I am sugesting to put a button in the recovery dialogs when you open an old
project that links to that functionality or at least mention it in the
recovery dialog messages.

Another thing is that the use of that functionality is not very intuitive.
In order to select a new symbol you have to right click. One may expect a
context menu with that action. I sugest a left click or a double left click
to select a new component.
```
Original tags: eeschema

Story points: 14.0
Fatal crash eeSchema V5 assigning footprint (lp:#1747546)

[Original report](https://bugs.launchpad.net/bugs/1747546) created by **Brian Piccioni (br0an)**
```
Application: kicad
Version: (2018-01-26 revision 54ebd4574)-makepkg, 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

When editing a specific component (resistor) to assign a footprint, if I
browse footprints, select R_1206 handsoldering and double click or select
"Insert Footprint in board" the footprint browser would crash and throw
error "Error unmapping vertices buffer:invalid operation".

After this, the browser would hang and all KiCad windows would no longer
function until all were killed via Task Manager.

This happened eveyr time I tried it until I decided to use CVPCB to assign
the footprint. After that the error was thrown once then disappeared and
even new parts would not cause a problem.

This was a file imported from V4 if that matters.
```
Original tags: eeschema

Story points: 14.0
Different width tracks may be disconnected when dragged (lp:#1747526)

[Original report](https://bugs.launchpad.net/bugs/1747526) created by **Novak Tamas (novak-7)**
```
If there are two different width segments connected, I click the connecting
point and push D to drag,
sometimes two segments get disconnected. Not a big problem as I get a
ratsnest line, so may be re-connected later. See attached video.


Application: kicad
Version: (2018-01-30 revision 342197bb3)-makepkg, 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: pcbnew

Story points: 10.0
GerbView (modern) doesn't load PT and NPTH holes after changing layer colors (lp:#1747443)

[Original report](https://bugs.launchpad.net/bugs/1747443) created by **Art (diametrix)**
```
I can reproduce this every time.  First I load all the layers.  Then change
layer color for any layer.  Then try to load both NPTH and PT layers.  Only
PT layer shows up in the layer manager.  All the holes appear correct.  If
at this point I go and try to load NPTH layer, it replaces PT layer in the
layer manager and both plated and non plated holes are displayed.  Some of
the holes appear with wrong sizes.  For example, I have a footprint with a
ground pad and small thermal vias.  Those show with the diameter of the
board non-plated mounting holes (which are quite large).  At this point
trying to load any other hole layer doesn't change the hole layer being
displayed.

Application: gerbview
Version: (2018-01-26 revision 0d532b43d)-makepkg, 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
```
Original tags: gerbview

Story points: 6.0
Duplicate block does not show duplicated block (lp:#1747431)

[Original report](https://bugs.launchpad.net/bugs/1747431) created by **Dominik B (matyro)**
```
I am using prebuild KiCad nightly dc66b73a2 from the 02.02.2018 on Windows
10

When I duplicate a single element in Eeschema booth the duplicated element
and the new (attached to my mouse) are displayed. When I duplicate a block
only the new element (attached to mouse) is displayed. The duplicated block
stays invisible until I finish the operation.
```
Original tags: eeschema

Story points: 6.0
NC flag cannot connect to hierarchical sheet pins (lp:#1747310)

[Original report](https://bugs.launchpad.net/bugs/1747310) created by **Niko Montonen (montonen-niko)**
```
Application: kicad
Version: 4.0.7 release build
wxWidgets: Version 3.0.3 (debug,wchar_t,compiler with C++ ABI 1011,GCC
7.1.0,wx containers,compatible with 2.8)
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0
nghttp2/1.23.1 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON

OS: Windows 10, not platform-specific

The NC flag cannot connect to hierarchical sheet pins.
I've seen at least a few people using hierarchical sheets as sort-of
modules, so they can be copied from one project to the next. In this use
case, it would be rather nice to be able to simply add the NC flag to
unused pins, rather than having to go inside the sheet, delete the label
and then add the NC there.

Picture to demonstrate: https://i.imgur.com/XQA9ay2.png
The "unconnected" indication box can be seen on the pin, even though the NC
flag is directly on top of the pin.
```
Original tags: eeschema erc feature.request

Story points: 6.0
schema: duplicate block makes original invisble (lp:#1747197)

[Original report](https://bugs.launchpad.net/bugs/1747197) created by **Nicholas Savenlid (nicholas-z)**
```
1: mark some objects
2: duplicate block
once you start to move your duplicated block the original becomes invisible
so it appears like a move operation

3: put your copy down, and the original becomes visible again

Application: kicad
Version: (2018-02-02 revision dc66b73a2)-makepkg, 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
```

Story points: 26.0
pcbnew, track hidden under footprint cannot be dragged (lp:#1747156)

[Original report](https://bugs.launchpad.net/bugs/1747156) created by **Nicholas Savenlid (nicholas-z)**
```
trying to grab a drag to drag it will fail if the track is covered by a pad
on same layer

even if footprint layer is turned off the problem remain, you can only get
hold of the track-part once it exits from the pad.

video can be provided upon request, as my descriptions often are ...
unclear

Application: kicad
Version: (2018-01-30 revision 342197bb3)-makepkg, 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
```

Story points: 6.0
eechema search & replace (lp:#1747037)

[Original report](https://bugs.launchpad.net/bugs/1747037) created by **Franck78 (fbourdonnec)**
```
Hello,

The search&replace ignores the field LIBRARY NAME shown on left when you
edit a component.

$Comp
L IRF540N Q18    <==== need text editor to search&replace this field
"IRF540N"
U 1 1 57D95DEA
P 24650 20050
F 0 "Q18" H 24300 19900 50  0000 L CNN
F 1 "IRL540N" H 24300 19800 50  0000 L CNN
F 2 "TO_SOT_Packages_THT:TO-220_Neutral123_Vertical_LargePads" H 24250
20150 50  0001 L CIN
F 3 "" H 24650 20050 50  0000 L CNN
 1    24650 20050
 1    0    0    -1
$EndComp

The dialog box clearly says : "search all fields' component"

Kicad version 4.0.7
```
Original tags: editing mass

Story points: 10.0
Wishlist: Hotkey in 3D Viewer to toggle Silk on/off (lp:#1746950)

[Original report](https://bugs.launchpad.net/bugs/1746950) created by **Tim N. Tashpulatov (tim-tashpulatov)**
```
Would be great to be able to quickly toggle Silk layer(s) visibility.
```
Original tags: 3d-viewer hotkeys

Story points: 6.0
Pcbnew print function autofits hidden text (lp:#1746911)

[Original report](https://bugs.launchpad.net/bugs/1746911) created by **Henrik Sandaker Palm (hspalm)**
```
Using File->Print function and ticking "fit in page". The area that is
fitted includes hidden text, but the text is rightfully not shown, only the
area is included.

Not all text is tried fitted. With the standard C_0805 footprint there is
an extra ref.des. text on F.Fab layer that is not linked to the component
with a blue airwire, which the print-fucntion does not try to fit (if it's
Visible or Invisible).

The selection of layers to include in the print does not seem to affect the
fitted area.

The behavior is not affected by the rendering option to show/hide "hidden
text".

The included file is a Pcbnew project with the C_0805 footprint.
The footprint is placed arbitrarily,
the Value-field (F.Fab) is Invisible and is placed above the footprint,
the Ref.Des.-field (F.silk) is Invisble and placed to the right of the
footprint,
The extra ref.des.-field (F.Fab) is Visible and placed to the left of the
footprint.

I then go to File->print and preview the print with options "fit in page"
ticked, and "print frame ref" unticked. The Footprint shows in the bottom
left of the preview corner with no other text showing.

For some reason, my hidden Ref.des. field is not greyed out when checked
Invisble until I hide F.Silk. layer. I've not seen this behavior before, it
would be interesting to see if it follows the Pcbnew file or if it's my
Kicad install.



Application: kicad
Version: 4.0.6 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1010,GCC
6.3.0,wx containers,compatible with 2.8)
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON
```
Original tags: pcbnew printing

Story points: 10.0
pcbnew ask about clarification between footprint and pads (lp:#1746899)

[Original report](https://bugs.launchpad.net/bugs/1746899) created by **Nicholas Savenlid (nicholas-z)**
```
Pcbnew should not ask about clarification between pads and footprint if
footprints has the pads locked

see attached picture

Application: kicad
Version: (2018-01-30 revision 342197bb3)-makepkg, 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
```

Story points: 6.0
Default fields don't get instantiated until Symbol Properties is opened (lp:#1746814)

[Original report](https://bugs.launchpad.net/bugs/1746814) created by **Janis Skujenieks (janis-skujenieks)**
```
If I add default fields in "Schematic Editor Options" they are not included
in BOM until I specifically open symbol properties and press OK. You can
change some field values, but that is not necessary. That means I have to
open every symbol.

This is not BOM script problem because those fields aren't in xml file.

Application: kicad
Version: (2018-02-01 revision b42084524)-master, debug build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.57.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.29.0
Platform: Linux 4.14.14-1-ARCH 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.66.0
    Curl: 7.57.0
    Compiler: GCC 7.2.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=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```
Original tags: bom eeschema fields

Story points: 22.0
Cursor freezes in pcbnew, again (lp:#1746507)

[Original report](https://bugs.launchpad.net/bugs/1746507) created by **eelik (eelik)**
```
See also Bug #1716702, https://bugs.launchpad.net/kicad/+bug/1716702, and
also Bug #1745981, https://bugs.launchpad.net/kicad/+bug/1745981.

A similar, but not indentical, bug has occured in recent nightly builds.

Create a board with two overlapping items, for example graphic lines with
overlapping end points. Use the RMB to open the context menu, clarify
selection, open Properties, click OK. Now zooming with the middle mouse
button is stuck to a one point.

There have been so many of similar bugs with the mouse cursor (or the point
which is active for mouse actions) that it makes me wonder if there's
something wrong with the code architecture. I hope these can be fixed for
good.




Application: kicad
Version: (2018-01-30 revision 342197bb3)-makepkg, 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
```

Story points: 10.0
Layers grayed out in Footprint Editor (lp:#1746279)

[Original report](https://bugs.launchpad.net/bugs/1746279) created by **syl20j (syl20j)**
```
In the Footprint Editor, the layers Dwgs.User, Cmts.User, Eco1.User,
Eco2.User are grayed out, so it’s impossible to add comments (text) or draw
zones (with graphic lines or polygons) on these layers to define a keepout
area for example. Consequently, a footprint designer like me have to choose
another layer and change it after, by the the intermediary of the
properties dialog box (or with an external text editor). why not let the
choice to use these 4 layers to the footprint designer ?
```
Original tags: fpedit pcbnew

Story points: 50.0
cursor freezes in pcbnew after removing a corner of zone (lp:#1745981)

[Original report](https://bugs.launchpad.net/bugs/1745981) created by **eelik (eelik)**
```
I can reproduce this with a blank board.
1. Create a zone.
2. delete a corner of the zone.
3. Open DRC Control.
4. Start DRC.
5. Try to zoom with the middle mouse button. The cursor is locked to the
point where the corner was deleted.

This may happen under some other conditions, too, because this cursor
freezing has happened after doing something with zones but without running
DRC. But as far as I can remember it has always involved something with
zones. It has happened with several nightly builds from January, on Linux
and Windows (although I just found out this one way to replicate it on
Windows).

Application: kicad
Version: (2018-01-29 revision d44494bed)-makepkg, 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: cursor mouse pcbnew zones

Story points: 10.0
Mouse warps after context-menu-dialogs not useful (lp:#1745731)

[Original report](https://bugs.launchpad.net/bugs/1745731) created by **Jeff Young (jeyjey)**
```
It's useful to warp back to the context-menu-open-point after selecting an
interactive tool, but not after clicking OK or Cancel to a dialog which was
selected.

Exceptions would include dialogs which are preludes to an interactive tool,
such as zone creation, but I don't think you can get any of those via a
context menu.

For the long (and bloody) history, see:
https://bugs.launchpad.net/kicad/+bug/816739
```

Story points: 34.0
Open recent list has only 9 recent projects (lp:#1745729)

[Original report](https://bugs.launchpad.net/bugs/1745729) created by **Timothée Manaud (timothee)**
```
The "Open recent" list is very useful but is also too limited.
As I work with at least 15 project, in multiple revision, I find it useless
as the project I'm looking for is never in the list.
Why only 9 items? When most display nowaday have huge number of pixel.

Version:
Application: kicad
Version: no-vcs-found-bf44d39~61~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.13.0-26-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=ON
```

Story points: 12.0
Decide what locked means in pcbnew and implement it uniformly (lp:#1745627)

[Original report](https://bugs.launchpad.net/bugs/1745627) created by **Jeff Young (jeyjey)**
```
Different opinions exist about whether it should be "completely locked" or
just "geometrically locked" or something else.

It also appears that even within those definitions that pcbnew isn't
consistent.

See https://bugs.launchpad.net/kicad/+bug/1066220.
```
Original tags: pcbnew

Story points: 64.0