giseldo/neodataset huggingface dataset:
Bold text cutoff in GTK (lp:#1836498)

[Original report](https://bugs.launchpad.net/bugs/1836498) created by **Ian McInerney (imcinerney)**
```
In the confirmation dialog that asks about unsaved changes when you close
the window there is some text being cutoff. It appears to be related to the
use of wxRichMessageDialog, since it only effects libedit on Linux (every
other unsaved changes dialog uses the normal wxMessageDialog). See the
attached screenshot for an example. The text should have "closing?" visible
on the end, and also the lower extents of the lower row of text are cutoff
(e.g. the bottom of y, p, etc.).

I think this is more of a wx bug than a KiCad bug, but I don't know which
platforms it affects. Do any OSX devs see this in any of the dialogs? All
of the unsaved changes confirmation dialogs there use the rich message. Is
this visible in libedit on Windows?



Application: LibEdit
Version: (5.1.0-1255-g20036f810-dirty), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1c 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.37.0
Platform: Linux 5.1.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: Clang 8.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
```
Original tags: eeschema gtk ui wxwidgets

Story points: 6.0
PCBNew ENTER should close Eidt Props window (lp:#1836492)

[Original report](https://bugs.launchpad.net/bugs/1836492) created by **Barry Buelow (iabarry)**
```
PCBNew 5.1.2

When editing parameters, closing the window requires clicking the button.
Since hands are on the keyboard, it would be convenient to have ENTER
accept the edit and close the window.  Shift + Enter could be use to start
a new line if needed.

thanks
barry
```

Story points: 6.0
Asymetric scale removed from print dialog of 5.1.2? (lp:#1836473)

[Original report](https://bugs.launchpad.net/bugs/1836473) created by **Rene Poeschl (poeschlr)**
```
Most home printers require slightly different scale settings in x and y
direction to get a perfect printout for home edging. In the past KiCad had
the option to scale x and y independently in the print dialog. This seems
to have been removed. Is there a good reason for this or was this an
accident?
```
Original tags: printing

Story points: 12.0
pcbnew button available with no project open after running pcbnew standalone once (lp:#1836460)

[Original report](https://bugs.launchpad.net/bugs/1836460) created by **Simon Richter (sjr)**
```
I just installed onto a new machine, with no previously existing kicad
config in the home directory.

Then:

 - open "kicad" (no project history, no project open, eeschema/pcbnew
disabled)
 - close window
 - open "pcbnew" (gives black canvas for me, probably unrelated)
 - close window
 - open "kicad" again

The pcbnew button is not disabled now, clicking it gives a dialog stating
that ".kicad_pcb" doesn't exist. Dismissing that dialog disables the pcbnew
button.

Video: http://psi5.com/~geier/kicad-init.ogv
```
Original tags: ui

Story points: 6.0
[eeschema][Linux] certain grid dots dissapearing after zoom or middle mouse drag (lp:#1836457)

[Original report](https://bugs.launchpad.net/bugs/1836457) created by **Lada (sumis)**
```
Hello all,

I noticed an interesting behaviour of the grid dots in eeschema in version
5.1.2 on Linux (Fedora 30). The thing is that sometimes (but very often)
when I zoom/unzoom or drag ussing the middle mouse button, the "minor" grid
dots disappear and only the "big ones" remain. A left click or change of
zoom usually bring the missing dots back. Please see the attached short
screen capture documenting this.

Window version 5.1.2 does not exhibit this behaviour (tested on the same
computer via dualboot). Also Linux version 5.0.2 does not do this. I also
experimented with building using GTK+ 2 and 3, but this made no difference.
Running a custom build of 5.1.2 or Fedora's package doesn't make a
difference either. This suggests that this might be Linux (Fedora?) and 5.1
specific thing.

I'll gladly play with more combinations and provide more details if you
want me to.

The details for the build used in the screen capture:

Application: KiCad
Version: (5.1.2-194-gf11d95044), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1c zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0
libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.8.7/openssl/zlib nghttp2/1.38.0
Platform: Linux 5.1.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+ 2.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=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
GerbView does not open a gerber-job (.gbrjob-file)  (lp:#1836448)

[Original report](https://bugs.launchpad.net/bugs/1836448) created by **DDuck007 (dduck007.01)**
```
The .gbrjob-file is not opened in GerbView - no gerber file is loaded.

Version:
Application: KiCad
Version: (5.1.0-1258-gf2f2b4bcf), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.65.0 OpenSSL/1.1.1b (Schannel) zlib/1.2.11 brotli/1.0.7
libidn2/2.1.1 libpsl/0.21.0 (+libidn2/2.1.1) nghttp2/1.38.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.70.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.65.0
    Compiler: GCC 8.3.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: gerbview

Story points: 6.0
Add preference for whether Flip flips across X or Y axis (lp:#1836267)

[Original report](https://bugs.launchpad.net/bugs/1836267) created by **Jeff Young (jeyjey)**
```
We currently flip across X (like a flip-chart).

I'd like it to flip across Y (like pages of a book).
```
Original tags: feature.request pcbnew

Story points: 18.0
pcbnew and footprint editor: export selection as dxf (lp:#1836231)

[Original report](https://bugs.launchpad.net/bugs/1836231) created by **Dino Ghilardi (dino-ghilardi)**
```
Introduction:
-The 2d drawing capabilities in kicad for lines are limited and creating
complex shapes is easier using a different 2D CAD (librecad, autocad
etc...) to create a dxf file and then import it in pcbnew or footprint
editor with file->import->graphics.
-A whole layer in pcbnew can be exported in dxf format using plot and
choosing dxf format, but this option is not available in the footprint
editor.


Wish:
It should be useful being able to select a group of 2D lines (as a board
outline or a component silk screen etc) and export just the selection
without the need to export the whole layer.

Typical usage case:
Create a 2D shape in an external CAD
Import in kicad
Modify it in kicad
At the change number 12345 you figure out that the next step would be much
easier using the librecad tool "xyz", but editing the original dxf file
implies re-doing the 12344 changes you made in kicad.
so [new feature]: Export the outline you need to change in dxf format
modify it in librecad (or autocad or any..cad)
re-import in kicad.


At least this wishlist can be reduced to "add dxf export or dxf plot to
footprint editor" (probably it would be easier/faster to implement)

Cheers,
Dino.
```
Original tags: dxf export feature.request pcbnew plot

Story points: 12.0
Update footprint does not reset text visibilities (lp:#1836183)

[Original report](https://bugs.launchpad.net/bugs/1836183) created by **Romain (romain145)**
```
In the "Update Footprints from Library" window (attached), when replacing a
footprint the visibility of the text on the F.Fab layer does not change
despite the box "Reset text layers and visibilities" being ticked.
I have made the Value field (on the F.Fab layer) invisible and saved the
footprint, but the change is not taken into account.

Expected behaviour: if the box "Reset text layers and visibilities" is
ticked, the visibility should be updated.
Actual behaviour: the visibility of the text is not updated.
Workaround: ticking the box "Reset text sizes, styles and positions" does
change the visibility and resets the position of all texts.


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: pcbnew

Story points: 6.0
Default selected button in close confirmation dialogue is "Discard Changes" on GTK (lp:#1836178)

[Original report](https://bugs.launchpad.net/bugs/1836178) created by **Alexander Willer (awiller)**
```
Affects all applications.

When switching the active footprint, symbol or closing the application
window while having unsaved changes, the appearing confirmation dialog has
"Discard Changes" selected as the default option.

"Cancel" or "Save Changes" should be the default selected option to prevent
data loss. In my opion, "Cancel" would be the better choice, since it
doesn't alter any data by accident (in contrast to "Save Changes".

Application: kicad
Version: 5.1.2-1.fc30, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1c zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0
libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.8.7/openssl/zlib nghttp2/1.38.0
Platform: Linux 5.1.5-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.0.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: ui

Story points: 6.0
Transparant images in page layout get dark background in PDF (lp:#1836173)

[Original report](https://bugs.launchpad.net/bugs/1836173) created by **Seppe Stas (seppestas)**
```
When using transparant images in a page layout, the images gets a dark gray
background when exporting a sheet or a layout to PDF.

I think using images with a transparant backround makes sense because they
work on both a dark background like the layout editor and light backgrounds
like PDF exports and the default schematic editor color scheme.

The image is rendered correctly in the schematic and layout editors.

See attached images.
```

Story points: 6.0
Symbol Editor - Can't edit arc radius (lp:#1836116)

[Original report](https://bugs.launchpad.net/bugs/1836116) created by **Seth Hillbrand (sethh)**
```
I just tried out the new arc tool in libedit and there's a lot to like.  It
is nice to be able to edit the end points directly.

However, I can't adjust the arc angle.  All arcs appear to draw at 180º.

I think it would be a good idea to unify the arc editors between libedit
and pcbnew/modedit.  In this case, drawing the initial arc as center ->
start -> end with a helper overlay would be good.  Then, when editing, use
the mid-point editor to allow making the arc shallower or deeper while
keeping the end points fixed.

Additionally, it would be good to include the arc parameters as editable
values in the arc properties window.

Application: LibEdit
Version: (5.1.0-1258-gad7ec3873), release 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
```
Original tags: eeschema

Story points: 6.0
Spice: Add check/warning for known irregularities in implicit models (lp:#1836115)

[Original report](https://bugs.launchpad.net/bugs/1836115) created by **J D (john-doe-dev)**
```
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



Kicad uses the IPC convention of assigning diode cathodes as pin 1 and
anode as pin 2, while the spice simulation engine uses pin 1 as anode.
Although spice models are not included in (most of?) the kicad built-in
libraries, the system appears to recognize diodes and generate a default
spice diode element. The difference in the spice and kicad/IPC conventions
results in incorrect simulations without warning to the user. Additionally,
at no point during use is the user warned that the common diode symbols are
incompatible with the spice simulation feature.

While this is not strictly a bug in the software or mistake in the library,
the two combined results in a significant failure during actual use of the
spice simulation feature.
```
Original tags: eeschema ngspice

Story points: 6.0
DXF import : allow case-insensitive extension (lp:#1836086)

[Original report](https://bugs.launchpad.net/bugs/1836086) created by **fenugrec (fenugrec)**
```
(feature request, not really a bug)
In Pcbnew, the file-open dialog for importing a dxf file only accepts
lowercase ".dxf" extensions.

Would it be possible to modify the wildcard (probably around
https://git.launchpad.net/kicad/tree/pcbnew/import_gfx/dxf_import_plugin.h#n149
) to accept either a case-insensitive match, or at least both .DXF and .dxf
?

Thanks!

Kicad 5.1.2 on linux x86_64
```

Story points: 6.0
Modedit: Upper/lower case in new footprint name can cause overwriting existing file without confirmation. (lp:#1835999)

[Original report](https://bugs.launchpad.net/bugs/1835999) created by **Grzegorz Obuch (grzegorzobuch)**
```
Saving a new module with a name containing only a different letter case
overwrites the old one without confirmation.

Application: ModEdit
Version: (5.1.0-1241-g30ec895c9), 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:
    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 windows

Story points: 6.0
Eagle import does not respect pad mask settings (lp:#1835930)

[Original report](https://bugs.launchpad.net/bugs/1835930) created by **Grzegorz Obuch (grzegorzobuch)**
```
Pad after importing to kicad always have the mask layer activated,
regardless of the settings in the eagle.

Example pad in eagle:

<smd name="A" x="-1.35" y="1.75" dx="2.3" dy="2.5" layer="1" stop="no"
cream="no"/>

after import in Kicad pad F.Paste layer is switched off, but F.Mask is
switched on..

For stable version 5.1.2 it works the same.

Application: Pcbnew
Version: (5.1.0-1195-g1548dcfe8), 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:
    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
Cross ref in schematic text (lp:#1835921)

[Original report](https://bugs.launchpad.net/bugs/1835921) created by **Hildo Guillardi Júnior (hildogjr)**
```
Seeing that KiCad is having a effort to update the text box behavior /
features, I propose a new one.
By some code as `\ref{ID_PART1}` the text will create a cross reference
(maybe in the future also hyperlink in the PDF centralizing the referenced
part) that will appear in the text as the reference of the part.

For example, the parts:
R1 -> ID_PART1
R2 -> ID_PART2
R3 -> ID_PART3

In the text:
`\ref{ID_PART1}` became 'R1'
`\ref{ID_PART1, ID_PART3}` became 'R1, R3'
`\ref{ID_PART1, ID_PART2, ID_PART3}` became 'R1-R2'

This will help to do documentations in the project that always have the
correct reference (example: "assemble \ref{ID_PART1} in case of..." will
never refer to a wrong component, if the parts are re-annotated).

To create a good user experience, the text input dialog (in Eeschema and
Pcbnew) could have a button "Add ref" that opens a list of components or
allow click in one to take the UNIQUE ID / TIME STAMP.

Also: the text boxes should be be update in Eschema always that the
"Annotate Schematic" run and in Pcbnew always that sync with Eschema. In
case of not present the ID anymore, the text could be "REF ERRO!".


Application: Eeschema
Version: 6.0.0-unknown-3a8f32c~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-54-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 feature.request

Story points: 6.0
Eeschema crashing extraordinarily frequently (lp:#1835907)

[Original report](https://bugs.launchpad.net/bugs/1835907) created by **Ron Burkey (rburkey)**
```
Recently, eeschema has been spontaneously crashing very frequently.
Yesterday it crashed for me perhaps two dozen times.  I've not reported it
because I couldn't reproduce it. However, I found a reproducible case this
morning, using the current nightly.

What you see in the linked video
(https://drive.google.com/open?id=15YeV1E9CO4MgU8pfzFPE8cPrTKNE06Ce) is me
beginning a net-highlight operation, then deciding instead to do a place-
component operation.  (Notice that even though I click the place-component
button, eeschema still remains in net-highlight mode.)  I then click the
net-highlight button again, but eeschema (and kicad as well) crash.  This
seems to happen almost every time I try that particular combination of
operations, but there are other combinations (which I can't presently
identify) that have the same effect.

For what it's worth, here's a zipfile containing the schematic I am working
on in the video:
https://drive.google.com/open?id=10DCzQk6ShE6tyR7gv_M57SUXi1Ty3JEP.  The
video is of the top-level sheet, module.sch.  It may or may not be relevant
that this schematic has a bitmap image in the background template, which
I'm using to position objects during placement.  Another perhaps-novel
feature is that the sheet itself also has a small bitmap image (a logo)
that's not visible in the video.

Application: Eeschema
Version: 6.0.0-unknown-3a8f32c~86~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-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

Story points: 6.0
GerbView Incorrect display on Paste layer (lp:#1835895)

[Original report](https://bugs.launchpad.net/bugs/1835895) created by **MichaelM (noidemmedion)**
```
In GerbView some features on Paste displayed with wrong diameter and
offset: Paste for two round pins is offset to the right (by ~ one radius)
and displayed diameter is ~2 times smaller. GCPreview shows no problems.
Screenshots from both and gerber files in attached zip file.
```
Original tags: gerbview

Story points: 6.0