giseldo/neodataset huggingface dataset:
Editing a footrpint from the current board (lp:#1735455)

[Original report](https://bugs.launchpad.net/bugs/1735455) created by **Art (diametrix)**
```
If you attempt to edit a footprint from the current board (Ctrl-E), the
footprint is opened with all the editing that has been done at the board
level (i.e. position, appearance and text of reference and value fields).
This reduces functionality of the shortcut.  If you attempt to save such
footprint into a library, all the data fields will be save with that
editing. For example, if your components reference was U5 it is going to
get saved as U5 in the library, instead of REF**  One can say that you are
just editing the specific footprint of the current board and not the
footprint from the library.  I don't see a lot of utility to such approach.

There might be some isolated cases when this can come handy, but as a rule
I would rather drive the layout based on the library footprints and have a
shortcut when I can rapidly access a footprint from a design and open it
from the library without trying to find which library it belongs to and
then go find the library and then try to find it in the library.  It would
be even better if the library that the footprint belongs to was already
selected when I open it with a CTRL-E shortcut, so all I would have to do
after editing a footprint would be hit "Save to the library" and then
update the footprint at the board level.
```

Story points: 10.0
Symbol preview in Cvpcb (lp:#1733930)

[Original report](https://bugs.launchpad.net/bugs/1733930) created by **Martin (martin-marmsoler)**
```
Hello,

in Cvpcb it is possible to show a preview of the footprint, but it would be
also nice if there is a possibility to show the symbol. So you can check if
the parts fit together (for example: Diode symbol pins: 1,2 and in the
footprint it is A,K. It takes some time to find the problem why the
footprint has no connection to it.)

Best regards,

Martin
```
Original tags: eeschema

Story points: 14.0
PcbNew minimal zoom problem (lp:#1733067)

[Original report](https://bugs.launchpad.net/bugs/1733067) created by **Cezary Zieliński (olek13)**
```
Zooming PCB view in the direction of ever smaller magnification (under
0.55), finally the PCB image completely disappears. Problem exists
practically in all nightly builds (in stable 4.07 version too), Windows and
Linux, but only on Hi-Res monitor (I use Philips 4k LCD monitor). On a
"normal" FULL HD LCD everything is OK.

Application: kicad
Version: (2017-11-17 revision 10de79260)-master, 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: hdpi

Story points: 6.0
3D Viewer (Latest Nightly Build): Raytracing bottom of board, lights, shadows, reflections, etc. Do not flip with the camera.  (lp:#1732993)

[Original report](https://bugs.launchpad.net/bugs/1732993) created by **Jt Whissel (jtwhissel)**
```
When using raytracing, the shadows, reflections, lights do not move. When I
switch it to "back view" I would expect the board to flip and not the whole
"world"/scene around the board. Maybe even add a button to "flip" the board
like there is in pcbnew. I attached some sample renders to show you what I
mean. There is one of the top render and one of the back render. They
should be identical as far as I believe the intended behavior should be.

Thanks for your time guys!


Application: pcbnew
Version: no-vcs-found-a655486~61~ubuntu17.10.1, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0
(+libidn2/2.0.2) librtmp/2.3
Platform: Linux 4.13.0-16-generic 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.62.0
    Curl: 7.55.1
    Compiler: GCC 7.2.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: 3d-viewer raytrace

Story points: 18.0
Allow thermal relief options for custom pads (lp:#1732720)

[Original report](https://bugs.launchpad.net/bugs/1732720) created by **James Jackson (james-a-f-jackson-2)**
```
When creating a footprint with a custom pad shape, copper fills do not
recognise the net assigned to the pad, and therefore the copper fill does
not reach the pad.

Minimal example attached - one custom footprint with one regular pad and
one custom pad, each assigned to the same net.  The regular pad receives
the copper pour whereas the custom pad does not.

Version is from a recent nightly, details below:

Application: kicad
Version: (2017-10-23 revision a562525)-master, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.43.0 SecureTransport zlib/1.2.5
Platform: Mac OS X (Darwin 15.6.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.2 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.61.0
    Curl: 7.43.0
    Compiler: Clang 7.3.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_SPICE=ON
```
Original tags: copper footprint pad pcbnew pour

Story points: 72.0
Component Table View from PcbNew (lp:#1731952)

[Original report](https://bugs.launchpad.net/bugs/1731952) created by **Hildo Guillardi Júnior (hildogjr)**
```
I think the "Component Table View" could be implemented even in the Pcbnew,
not just in the Eeschema.

One of the interesting functionalities could be:
1) Change the text font of all selected items (I saw that Font
interpretation is in the road map to future versions);
2) Change the text orientation (for example: usually I want all horizontal
left-to-rigth and all vertical bottom-to-top, to make a easy way to read
the PCB silk stamped);
3) Change multiple footprints at same time (I know, this is already in the
"Footprint Proprieties").
```
Original tags: feature.request

Story points: 6.0
Unclear errors when trying to load Eagle binary format (lp:#1731129)

[Original report](https://bugs.launchpad.net/bugs/1731129) created by **Chris Pavlina (pavlina-chris)**
```
The footprint library table/wizard dialogs don't give any indication that
we don't support Eagle binary file formats, and when trying to actually
parse a library (because a user didn't know binary wasn't supported) it
gives an unclear error message. I think we should rename "Eagle" in the
format list to "Eagle XML", and replace the "not well-formed (invalid
token)" errors with something clearer.
```
Original tags: eagle import pcbnew ui

Story points: 6.0
Pcbnew: Position Relative feature offsets footprint placement (lp:#1730066)

[Original report](https://bugs.launchpad.net/bugs/1730066) created by **Sujith (sujitth)**
```

Issue:
1- when placing the footprints using the 'Position Relative' feature
vertically- I have entered the Move
   vector Y value and placed the footprint, but it got placed with a X
offset too.Placing horizontally no
   issues.

2- now after rotating the footprint-placing vertically no issues, but the
horizontal placement offsets.

so, it seems there is an offsetting issue in one of the axis that depends
on the footprint position.

Version:

Application: kicad
Version: (2017-10-31 revision 05ab44f46)-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 starter

Story points: 14.0
Eagle schematic import title block issue. (lp:#1729722)

[Original report](https://bugs.launchpad.net/bugs/1729722) created by **Wayne Stambaugh (stambaughw)**
```
The Eagle schematic importer attempts to import the title block but maps it
to the same position from the Eagle schematic which overlaps the default
KiCad worksheet.  It should either not import the title block or create a
custom worksheet from the Eagle import add it to the schematic file.  My
preference would be the latter.  I've attached a PDF plot of the issue but
every Eagle schematic I've imported with a title block shows the same
issue.

Application: kicad
Version: (2017-11-01 revision e5c4cfc3b)-master, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.56.0 OpenSSL/1.0.2l (WinSSL) zlib/1.2.11 libidn2/2.0.4
libssh2/1.8.0 nghttp2/1.26.0
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.56.0
    Compiler: GCC 7.2.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_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```
Original tags: eagle.import

Story points: 8.0
"Open documentation" - environment variable not working (lp:#1729276)

[Original report](https://bugs.launchpad.net/bugs/1729276) created by **michalstec (nnn4000)**
```
I used to use relative paths to access documentation files in eeschema.
After recent changes in accessing doc files it doesn't work.
I tried to use environment variables KICAD_SYMBOL_DIR or KIPRJMOD to avoid
putting absolute paths in libraries. I noticed that when I put component to
the schematic, open Component Properties and click Show Datasheet then the
documentation file opens (datasheet field value filled with path
$KIPRJMOD/doc/Datasheets/Diodes/1N4007-E3_54.pdf) but when I try to open
documentation from the components context menu then I get message:
Doc File '$KIPRJMOD/doc/Datasheets/Diodes/1N4007-E3_54.pdf' not found



version 201710311449+05ab44f~61~ubuntu14.04.1

Application: kicad
Version: no-vcs-found-05ab44f~61~ubuntu14.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Platform: Linux 3.19.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.54.0
    Curl: 7.35.0
    Compiler: GCC 4.8.4 with C++ ABI 1002

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
Print track gray (lp:#1729060)

[Original report](https://bugs.launchpad.net/bugs/1729060) created by **Hildo Guillardi Júnior (hildogjr)**
```
Some time we need to print the PCB to check footlitos / CI packages or for
a visual analysis. We usually print as black-whit and all layers in one
page to save paper.

One interesting resource (option) will be "print tracks as a shadow / gray"
(when black-white is selected), or even print just the pad (THT and SMD)
not the tracks. Usually I did this in other softwares (example in
https://github.com/hildogjr/easyInverter/blob/master/Assemblies/2017-08-16%20Full%20inverter.PDF)
```
Original tags: feature.request

Story points: 14.0
Pcbnew python scripting: GetCornerPosition returns inaccessible Swig VECTOR2I pointer (lp:#1728611)

[Original report](https://bugs.launchpad.net/bugs/1728611) created by **Pietro Saccardi (5p4k)**
```
Version: (2017-10-23 revision a562525)-master, release build.
wxWidgets 3.0.2 Unicode and Boost 1.61.0
Platform: Mac OS X (Darwin 17.0.0 x86_64), 64 bit

Issue observed also in revision 537804b.

In Kicad nightly, `pcbnew.ZONE_CONTAINER.GetCornerPosition` returns a Swig
Object of type `VECTOR2I *`, which does not have any other method except
`append`, `acquire`, `next`, `own`, `disown`. It is thus not possible to
retrieve the coordinates via Python scripting.

Other related methods that return objects which are not accessible via
Python scripting are:

0. `pcbnew.ZONE_CONTAINER.GetCornerPosition` (returns a `VECTOR2I *`)
1. `pcbnew.SHAPE_POLY_SET.Outline` (returns a `SHAPE_LINE_CHAIN *`)
2. `pcbnew.SHAPE_POLY_SET.Vertex` (returns again a `VECTOR2I *`)
3. `pcbnew.SHAPE_POLY_SET.Iterate` and `CIterate` (return a
`SHAPE_POLY_SET::ITERATOR_TEMPLATE< VECTOR2I > *`)

This in particular means that there is no way of getting an zone outline.

Please see this topic for further details:
https://forum.kicad.info/t/python-scripting-reading-zone-outline/8302

We noted that:

1. `pcbnew.ZONE_CONTAINER.Outline` returns a `SHAPE_POLY_SET` in the
nightly, in comparison with the `CPolyLine` object that it returns in the
stable.
2. `VECTOR2I` is the returns value of the underlying C++ API in the
nightly, rather than `wxPoint`, and although they're structurally
identical, Swig seems unable to understand it.

Hope this helps.
```

Story points: 6.0
Open kicad_mod from project (lp:#1728442)

[Original report](https://bugs.launchpad.net/bugs/1728442) created by **Hildo Guillardi Júnior (hildogjr)**
```
In the main KiCad window we have the option to edit the kicad_mod related
to the project as text (by the mouse right button).

I think the default option have to be open this module in the own
package/footprint KiCad editor (also, maybe add a pre visualization in the
left blank space of this windows. That space is now sub utilized).
```
Original tags: feature.request

Story points: 6.0
Board-item-type-specific selection tools (lp:#1728428)

[Original report](https://bugs.launchpad.net/bugs/1728428) created by **Hildo Guillardi Júnior (hildogjr)**
```
Every time that you try to select something (some area) in Pcbnew,
independent of the tool that you are using (Route track, Add fooprint,...),
a window asking which kind of object do you want do select.

One more user friendly way is to move this interface as a toolbox that have
pre-seted option for which tool and the user can change, not being bothered
every time that try to select something.

This is a example how this feature could work:
https://www.youtube.com/watch?v=CDIbA_1SyfI.
```
Original tags: improvement

Story points: 6.0
Import SVG graphics to PCB (lp:#1728272)

[Original report](https://bugs.launchpad.net/bugs/1728272) created by **Hildo Guillardi Júnior (hildogjr)**
```
It will be interesting create a new graphical type in Pcbnew (as graphical
polygon, cicle, ...) to import SVG or others (vectorized) images formats
for any layer and keep the resizable propriety [edit: spun out to new
issue]

This will create the capability of add logos and others images to the board
without convert it to components or be locked up to one PCB layer (to
change it now is necessary to reedit in the library).

Even, the symbol library in PcbNew will be more versatile, not needing
different sizes.

NOTE: resizable graphics is now a separate issue:
https://bugs.launchpad.net/kicad/+bug/1817565
```
Original tags: dxf feature.request import svg

Story points: 26.0
gerbers zip (lp:#1728252)

[Original report](https://bugs.launchpad.net/bugs/1728252) created by **Hildo Guillardi Júnior (hildogjr)**
```
A option to output all the GERBERS files (with the drill files) in a ZIP
compressed file be a shortcut to the user to send this to manufacture
houses (also allow the Gerber View to open direct this ZIP file).
```
Original tags: export feature.request pcbnew plot

Story points: 22.0
PCBnew: value/ref locations and properties not hot-linked to footprint definition (lp:#1725201)

[Original report](https://bugs.launchpad.net/bugs/1725201) created by **Fredrik Atmer (fredrik-s)**
```
When changing position or font properties of the reference or value fields
in a footprint, this change does not happen to footprints already on the
board for any alternative on changing the footprint. Changing to a
different footprint and then back again works.

Is there another way to "reset" the fields to their default properties? Is
the above behavior a feature rather than a bug?


Application: kicad
Version: no-vcs-found-46edf65~60~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-93-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
```
Original tags: pcbnew

Story points: 12.0
No DRC error on Cut through track (lp:#1723600)

[Original report](https://bugs.launchpad.net/bugs/1723600) created by **Michal (mikon)**
```
If the PCB routing (drawing on PCB EDGES layer) crosses a track, no DRC
alert is indicated.
Experienced on 4.0.7 release, when doing stress relief routing on the PCB.
```
Original tags: 4.0.7 drc

Story points: 8.0
simulation: localized value prefixes (lp:#1721933)

[Original report](https://bugs.launchpad.net/bugs/1721933) created by **Eldar Khayrullin (eldar)**
```
Now spice component value prefixes (f, k, meg and etc) are i18n in Dialog
`Edit spice model`.
It'll be cool if eeschema put to simulator right prefixe substitution if
one use own (case sensetive i18n) prefixes in accordance with previous
translated dialog.
Example (Russian):
М -> meg
к -> k
м -> m
мк -> u
п -> p
and etc.

Application: eeschema
Version: no-vcs-found-1164eaa~60~ubuntu17.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) librtmp/2.3
Platform: Linux 4.10.0-35-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.62.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_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```
Original tags: eeschema ngspice

Story points: 8.0
No relative paths for custom libraries on Windows (lp:#1721800)

[Original report](https://bugs.launchpad.net/bugs/1721800) created by **Todor Todorov (ttodorov)**
```
I am using KiCad on Windows 10, compiled from sources (branch master,
commit 1164eaab7). When I add my custom  libraries in eeschema, the project
file is saved with absolute paths, even when I elect to use relative paths
in the dialog. This prevents me from using the same project on Linux or on
another Windows computer, where my drives are organized in a different
manner.

Workflow:
1) create a new project
2) open eeschema
3) edit Preferences > Component Libraries
4) add a User defined search path
5) accept use of relative paths when offered
6) highlight the newly added folder in the Current search path list of the
dialog window
7) add a custom library

The library will show at the bottom of the Component library files list
with full path name. There is one important fact to notice: the new search
path is added to the search path list at the bottom of the window as a
relative path!

Please note the attached picture eeschema_symbol_paths_REV1.png and the
project file ws2812_aquarium_REV1.pro

The peculiar thing is that if I modify the workflow slightly, it works as
expected:
1) create a new project
2) open eeschema
3) edit Preferences > Component Libraries
4) add a User defined search path
5) accept use of relative paths when offered (notice, the search path list
shows the new folder as relative path!)
6) CLOSE THE DIALOG WINDOW WITHOUT ADDING NEW LIBRARIES
7) REOPEN Preferences > Component Libraries (notice, the search path list
now shows the new folder as absolute path1)
8) highlight the newly added folder in the Current search path list of the
dialog window
9) add a custom library

The new custom libraries are added to the used Component library files list
as basename only, without prepended path. The project file also lists them
by filename only. Please review attached screenshot
eechema_symbol_paths_REV2.png and corresponding project file
ws2812_aquarium_REV2.pro

I have noticed this problem in previous nightly builds as well. No idea, if
it is the same on Linux or Mac.
```
Original tags: eeschema

Story points: 6.0
pcbnew crash if "backing" up and place via (lp:#1721590)

[Original report](https://bugs.launchpad.net/bugs/1721590) created by **Nicholas Savenlid (nicholas-z)**
```
so lets try to explain:

1 track on F.fab already in place.

Tracks end mid air.

I want to continue routing on this track
(0.1mm wide)

but i want to place a via 1 step up the trace.

so i try to route the track backwards to make it shorter (0.05mm grid)
1 step diagonally up to the left.

but the trace budge and will not let itself be shortedned in lenght just
because i trace backwards over itself,

I think to myself, ok no problem, i put down my via here and cut the
remainder later.

crash.
```
Original tags: pcbnew

Story points: 6.0