giseldo/neodataset huggingface dataset:
DRC ignores traces crossing edgecut (lp:#1648055)

[Original report](https://bugs.launchpad.net/bugs/1648055) created by **Frank Severinsen (shack)**
```
Dear Kicad Developers

I found an issue with the DRC which I think would be worth looking into.
It seems the DRC doesnt check for traces crossing the edgecut.

Currently, the P&S router will happily push a trace out of the edgecut when
using the shove mode. (I am also making bug report on this)
for this reason the traces might go out of the outline without the user
even noticing it.
I would suppose simply treating the edge cut as any other trace would give
a DRC error when crossing the edgecut.
but perhaps having a seperate clearence to edgecut could be nicer since it
would allow the traces to go closer.

Though this is pretty easy to inspect manually, I believe the DRC should
provide the best possible chance for a functioning board.

tested on 4.0.4 and newest nightly

Greetings Frank Severinsen
```
Original tags: drc pcbnew

Story points: 50.0
I and U selection shortcuts work on hover track even when another is selected (lp:#1645670)

[Original report](https://bugs.launchpad.net/bugs/1645670) created by **Matthijs Kooijman (matthijskooijman)**
```
After using the interactive router / OpenGL view in pcbnew for a while, I
figured out that the "I" and "U" shortcuts ("copper connection" and
"trivial connection") work on the track the mouse is currently hovering
above.

Initially, I had assumed that these shortcuts worked on the currently
selected track. I found that the shortcuts behaved erratically, though,
sometimes they worked and sometimes they would not. Now I realize that this
depended on whether I had moved the mouse after selecting the track.
Looking back, I think my assumption came from the fact that other tools do
work on the selected element.

I would suggest extending these shortcuts so they also work with the
currently selected track. Now that I know about the hovering behavior, that
is easy to work with, but I think that working from the selected track
might also be useful (not in the least to prevent confusion with a new user
as I have found). I think there's two alternatives here:

 1. Whenever a track is selected, use it, even when the mouse hovers over
another track.
 2. Only when the track is not hovering over a track, use the selected
track (if any).

I think #1 would make the most sense, mostly to be consistent with other
shortcuts (I just tried E - edit, F - flip, ^D - duplicate, which all work
on hover only when no element is selected).

I have been using the 4.0.4 release, and also yesterday's version from the
4.0 branch for this.
```

Story points: 6.0
Eeschema - Pull Fields from Library (lp:#1643890)

[Original report](https://bugs.launchpad.net/bugs/1643890) created by **Justin Partain (justinwpartain1)**
```
At my workplace, we've been adding and updating default fields for our
entire library. As it stands, Eeschema has no means to pull this data from
the library. Even if the -cache.lib file is removed, that data is stored.
What is needed is a way to pull field data from the library.
```

Story points: 16.0
"Set grid origin" to some item's center (lp:#1643224)

[Original report](https://bugs.launchpad.net/bugs/1643224) created by **demidrol (dmitrodem-gmail)**
```
It would be nice to have command that sets the grid origin to component (or
pad, etc.) center.

A common use case for using this feature seems to be like this:
1. Draw board outline in librecad/solidworks/whatever
2. Put to the drawing some marks (like circles) to indicate the location of
LEDs, switches or other components which location should be fixed.
3. Import resulting DXF file to pcbnew
4. Place LEDs, switches, etc. according to "marks"

The attached patch adds this feature. One needs to select some item (like
circle on user dwg layer) and press Ctrl-Shift-X to place grid origin to
circle center.
```

Story points: 8.0
Property Inspector for Pcbnew

[Original report](https://bugs.launchpad.net/bugs/1640873) created by **Xavi Torres (xtm)**
```
It would very hepful when building the PCB (soldering components), to be
able to select components (Either in Schematic or PCB) with these two
methods:
 - One by one (By holding down the Shift key while clicking on the
component)
 - By parameters. For instance, select all components with value=10K and
Footprint=0603.

It also would be very hepful that, once multiple components are selected,
to be able to change (On all of them at once) any of their attributes:
Value, footprint, user field, name visibility in PCB, etc
```
Original tags: feature.request

Story points: 200.0
Add recently-used names to place label dialogs (lp:#1639719)

[Original report](https://bugs.launchpad.net/bugs/1639719) created by **Donald Palmer (donaldpalmer)**
```
I would like to make the following Feature Suggestion for eeschema.
When "Place net name - local label" it would be really helpful for eeschema
to offer already placed local labels to pick from. This would insure a typo
did not cause the user to create an extra net.
It would also make the placement of multiple labels go much faster.

Thank you for the software and consideration of this suggestion.
Info on system:
Version:4.0.4+e1-6308~48~ubuntu16.04.1-stable, release build
xxWidgets 3.0.2 Unicode and Boots 1.58.0
Platform:Linux 4.40-45-generic X86_64, 64 bit
```
Original tags: eeschema wishlist

Story points: 8.0
ERC does not find unconnected Power Ports (lp:#1639400)

[Original report](https://bugs.launchpad.net/bugs/1639400) created by **David Pearce (halzia)**
```
Eeschema bug
Power Ports have a "Pin" like a component symbol, but ERC does not flag if
the Power Port is not attached to a wire segment. The consequence is that a
Power Port can be placed on a wire and fail to name the net correctly,
resulting islands of isolated tracks.
The attached screenshot shows an "orphan" Power Port and an unconnected
resistor. The resistor IS detected by ERC

Application: kicad
Version: 4.0.4-stable release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1009,GCC
5.2.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.57.0
         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: eeschema erc

Story points: 30.0
Autoplot PDF etc when saving project (lp:#1636549)

[Original report](https://bugs.launchpad.net/bugs/1636549) created by **Frank Severinsen (shack)**
```
Hey Guys

thanks for the awesome job!

At my company we came up with a feature request, which I think could easily
be beneficial to others.
The idea is simply to add an option to automatically replot the PDF
whenever the schematic is saved.

It is often necessary to share the project on git with software developers
or other team members who only need to consult the schematics, without
applying changes.
As they would normally rely on the .pdf provided in the repository, it is
particularly important to keep it up-to-date with the .sch document.

Currently this is a manual process which is both time-consuming and prone
to being overlooked; by adding this feature the PDF would always reflect
the content of the schematics.

I made a quick mockup on how it could look but it is only meant as an idea
of how this could be implemented

Cheers
Frank Severinsen
```
Original tags: export

Story points: 30.0
user footprint plugins not found on OSX (lp:#1632321)

[Original report](https://bugs.launchpad.net/bugs/1632321) created by **Jonatan Liljedahl (kymatica)**
```
It seems user installed footprint wizard plugins are not found.

Looking at the code at
https://git.launchpad.net/kicad/tree/pcbnew/pcbnew.cpp?id=ea6b03cd5ffc6a902f197d7e9b8c23838e6cee9d#n253
it should be:

~/Library/Application\ Support/kicad/scripting/plugins/

Placing any plugin there does not show up. It does if I put it directly in
the installed app bundle:
/Applications/Kicad/kicad.app/Contents/SharedSupport/scripting/plugins/
```
Original tags: macos packaging python

Story points: 8.0
3D viewer doesn't show Filled Zones "cutouts" on Silkscreen layer or soldermask layer (lp:#1632068)

[Original report](https://bugs.launchpad.net/bugs/1632068) created by **firewalker (firew4lker)**
```
If someone lay a filed zone on a silkscreen layer, 3D viewer will show it
as a completely filled area without "cutouts" for the component under it.
It is correctly in the produced gerbers though.

http://i.imgur.com/q4cuD6S.png
http://i.imgur.com/f2ngSxM.png
http://i.imgur.com/i1FaCdV.png
http://i.imgur.com/k2UR9KO.png


Application: kicad
Version: (2016-10-07 revision f14dc8f)-master, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.50.3 OpenSSL/1.0.2j zlib/1.2.8 libidn/1.33
libssh2/1.7.0
Platform: Linux 4.7.6-1-ARCH i686, 32 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.61.0
Curl: 7.50.3
KiCad - Compiler: GCC 6.2.1 with C++ ABI 1010
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_SCH_IO_MANAGER=ON
                  KICAD_USE_OCE=ON
```
Original tags: 3d-viewer pcbnew

Story points: 38.0
schematic components get a ~ in front of their names and behave strangely when their value-text is hidden (lp:#1632048)

[Original report](https://bugs.launchpad.net/bugs/1632048) created by **Jan Krieger (jkriege2)**
```
Take any component, e.g. TEST from device.lib. It's definition in the file
looks like this:

#
# TEST
#
DEF TEST P 0 40 N N 1 F N
F0 "TP" 0 300 50 H V C BNN
F1 "TEST" 0 250 50 H V C CNN
F2 "" 0 0 50 H V C CNN
F3 "" 0 0 50 H V C CNN
DRAW
P 6 0 1 0 0 200 -50 150 0 100 50 150 0 200 0 200 N
X ~ 1 0 0 100 U 50 50 1 1 P
ENDDRAW
ENDDEF

and then hide its VALUE-field and save the lib in the symbol editr. The
component becomes:

#
# TEST
#
DEF ~TEST TP 0 40 N N 1 F N
F0 "TP" 0 300 50 H V C BNN
F1 "TEST" 0 250 50 H I C CNN
F2 "" 0 0 50 H V C CNN
F3 "" 0 0 50 H V C CNN
DRAW
P 6 0 1 0 0 200 -50 150 0 100 50 150 0 200 0 200 N
X ~ 1 0 0 100 U 50 50 1 1 P
ENDDRAW
ENDDEF

Note that now we have "DEF ~TEST" instead of "DEF TEST" before.

Best,
JAN
```
Original tags: eeschema

Story points: 6.0
Simulator freezes until return is pressed in terminal (lp:#1630676)

[Original report](https://bugs.launchpad.net/bugs/1630676) created by **Jonatan Liljedahl (kymatica)**
```
Most often (but sometimes not), running the simulator freezes the app,
until one switches to the terminal where kicad was started[1] and press the
return key a number of times, then the simulation completes. There's no
errors or Y/n questions in the simulator log or in the terminal.

[1] - At least on OSX, kicad must be started from the terminal with proper
environment variable set to make it find the needed ngspice init file and
codemodels.
```
Original tags: cern eeschema ngspice

Story points: 8.0
Initialization of ngspice on OSX (lp:#1630675)

[Original report](https://bugs.launchpad.net/bugs/1630675) created by **Jonatan Liljedahl (kymatica)**
```
On OSX, the installed bundle does not include the necessary codemodels and
init files for ngspice, so even though libngspice is bundled, one must also
install ngspice separately. This might be OK in itself, but the problem is
that kicad (or the bundled libngspice?) does not know where ngspice is
installed, so it does not find the needed files. A workaround is to start
kicad from the terminal and set an environment variable like this:

$ export SPICE_LIB_DIR=/Applications/ngspice/share/ngspice/
$ /Applications/Kicad/kicad.app/Contents/MacOS/kicad

This is not very user friendly.. ;)
```
Original tags: cern eeschema ngspice osx

Story points: 12.0
Deprecation warnings on OSX (lp:#1629330)

[Original report](https://bugs.launchpad.net/bugs/1629330) created by **xzcvczx (xzcvczx)**
```
The following functions/type have been deprecated since 10.9, as this was
released ~3yrs ago there is no guarantee of how much longer apple will keep
these functions around

common/gal/opengl/opengl_gal.cpp
    gluNewTess()
    gluTessProperty()
    gluDeleteTess()
    gluTessBeginPolygon()
    gluTessBeginContour()
    gluTessVertex()
    gluTessEndContour()
    gluTessEndPolygon()
    gluTessCallback()

utils/idftools/vrml_layer
    gluNewTess()
    gluTessCallback()
    gluTessProperty()
    gluTessNormal()
    gluDeleteTess()
    gluTessBeginPolygon()
    gluTessEndPolygon()
    gluTessBeginContour()
    gluTessEndContour()
    gluTessVertex()
    gluErrorString()

3d-viewer/3d_rendering/3d_render_ogl_legacy/ogl_legacy_utils.cpp
    GLUquadricObj
    gluNewQuadric()
    gluQuadricDrawStyle()
    gluQuadricNormals()
    gluCylinder()
    gluDeleteQuadric()
    gluDisk()
    gluSphere()



For the following 2 the recommended replacement from the deprecation notice
is GLXMatrix4MakePerspective (but that would require a later version of
opengl) It can also be replaced by
glm::perspective(http://stackoverflow.com/a/19647181) which wouldn't
require a later version of ogl

3d-viewer/3d_rendering/3d_render_ogl_legacy/c3d_render_ogl_legacy.cpp
    gluPerspective()
3d-viewer/3d_model_viewer/c3d_model_viewer.cpp
    gluPerspective()
```
Original tags: macos

Story points: 8.0
Pcbnew: "Layer" and "Render" visibility combination (lp:#1628702)

[Original report](https://bugs.launchpad.net/bugs/1628702) created by **Artsiom Shchatsko (cioma)**
```
I'd suggest making visibility settings in Pcbnew "Layer" and "Render" tabs
ANDed instead of ORed. I.e. an item is displayed on a certain layer only if
both this layer is enabled in "Layer" tab and this item type is enabled in
"Render" tab. Or even better: provide a user setting to select between
ANDing and ORing those visibility settings.
```
Original tags: pcbnew ui

Story points: 14.0
Pcbnew create array, produces same reference footprints. (lp:#1625964)

[Original report](https://bugs.launchpad.net/bugs/1625964) created by **firewalker (firew4lker)**
```
When using the create array function, the produced footprint use the same
reference.

Load a schematic netlist with a sequential part e.g. D1, D2,...,D10.
Load the netlist to pcbnew.
Delete every instance except D1.
Right click and select create array with 5 columns and two rows.
Every created footprint has the same reference D1.

Related thread: http://www.eevblog.com/forum/kicad/kicad-4-0-3-pcbnew-
making-a-footprint-array/


Also present in the latest git version.

Application: kicad
Version: (2016-09-20 revision c57fd7c)-master, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.50.3 OpenSSL/1.0.2h zlib/1.2.8 libidn/1.33
libssh2/1.7.0
Platform: Linux 4.7.4-1-ARCH i686, 32 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.61.0
Curl: 7.50.3
KiCad - Compiler: GCC 6.2.1 with C++ ABI 1010
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_SCH_IO_MANAGER=ON
                  KICAD_USE_OCE=ON
```
Original tags: array pcbnew

Story points: 30.0
spice simulator: dont' create Spice_Model field if it's equivalent to the implicit values (lp:#1624893)

[Original report](https://bugs.launchpad.net/bugs/1624893) created by **Eldar Khayrullin (eldar)**
```
I don't know is it intention or not but if I edit Spice Model the Value
field coping and creating the Spice_Model field. Then if I change the Value
field the Spice_Model field doesn't updated.
In simulator demos (e.g. sallen key sch) I don't see Spice_Model field but
if I edit spice model the Spice_Model field creates.

Application: eeschema
Version: 201609180819+7176~55~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-36-generic x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.58.0
Curl: 7.47.0
KiCad - Compiler: GCC 5.4.0 with C++ ABI 1009
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_SCH_IO_MANAGER=OFF
                  KICAD_USE_OCE=ON
```
Original tags: eeschema ngspice

Story points: 10.0
spice simulator: power symbol a floating point separator (lp:#1624890)

[Original report](https://bugs.launchpad.net/bugs/1624890) created by **Eldar Khayrullin (eldar)**
```
If I use a power symbol with comma separator (like +3,3V) the simulator log
shows:

Node                                   Last Voltage        Previous Iter
----                                   ------------        -------------
net-_c2-pad1_                                     0                    0
+3                                                0                    0
3v                                                0                    0
vc1#branch                                        0                    0

Spice think about two nodes +3 and 3v.

Application: eeschema
Version: 201609180819+7176~55~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-36-generic x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.58.0
Curl: 7.47.0
KiCad - Compiler: GCC 5.4.0 with C++ ABI 1009
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_SCH_IO_MANAGER=OFF
                  KICAD_USE_OCE=ON
```
Original tags: eeschema ngspice

Story points: 6.0
eeschema: Operations on blocks inner selection (lp:#1624686)

[Original report](https://bugs.launchpad.net/bugs/1624686) created by **Eldar Khayrullin (eldar)**
```
It will be usefull add selection tool that selects only elements in block
with mouse.
Now mouse selection catch all elements that touch to block rect.

Application: kicad
Version: 201609160817+7160~55~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-36-generic x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.58.0
Curl: 7.47.0
KiCad - Compiler: GCC 5.4.0 with C++ ABI 1009
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_SCH_IO_MANAGER=OFF
                  KICAD_USE_OCE=ON
```
Original tags: eeschema

Story points: 14.0
spice simulator: floating point separator (lp:#1624659)

[Original report](https://bugs.launchpad.net/bugs/1624659) created by **Eldar Khayrullin (eldar)**
```
If use a non-locale floating point separator in the Component Properties ->
Edit Spice model -> Value field and click OK I see a msgbox with the
message:
Error:
'2.2' is not a valid Spice value

Set value 2,2 - OK.

Application: kicad
Version: 201609160817+7160~55~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-36-generic x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.58.0
Curl: 7.47.0
KiCad - Compiler: GCC 5.4.0 with C++ ABI 1009
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_SCH_IO_MANAGER=OFF
                  KICAD_USE_OCE=ON
```
Original tags: eeschema ngspice

Story points: 6.0
Keep netnames of long tracks on-screen

[Original report](https://bugs.launchpad.net/bugs/1622273) created by **Chris Pavlina (pavlina-chris)**
```
The labels that are displayed on top of traces in pcbnew are very handy,
but they're always displayed at the center of the trace. It would be nice
if they could move when they would display offscreen, so you can zoom in on
a section of traces not including their centers and still see labels.
```
Original tags: cern gal pcbnew

Story points: 8.0
DRC dialog session confuses GAL router state (lp:#1621487)

[Original report](https://bugs.launchpad.net/bugs/1621487) created by **Dick Hollenbeck (dickelbeck)**
```
Regression: GAL mode, with track tool selected, run DRC. Although the
toolbar icon reverts properly to non-track mode, i.e. vanilla arrow mode,
the router internals remain in track layout mode. You can lay down track
after dismissing the DRC dialog, even though the track tool is not visibly
selected. This bug existed some time ago and was fixed, now broken again.
```
Original tags: gal pcbnew

Story points: 6.0
DRC reports with poor/bad coordinates (lp:#1619133)

[Original report](https://bugs.launchpad.net/bugs/1619133) created by **PCB Wiz (1-pcb-wiz)**
```
DRC on the design give this report

ErrType(23): Copper areas intersect or are too close
    @ (45.155 mm,-7.899 mm): Zone Outline  (00000000) [+5V] on In2.Cu
    @ (45.155 mm,-7.899 mm): Zone Outline  (00000000) [+12V] on In2.Cu
ErrType(23): Copper areas intersect or are too close
    @ (45.155 mm,-7.899 mm): Zone Outline  (00000000) [+5V] on In2.Cu
    @ (45.155 mm,-7.899 mm): Zone Outline  (00000000) [+12V] on In2.Cu


That is of course useless to identify actual issue, as missing is the
ACTUAL distance (which DRC must know, so please tell the user !), and it
has duplicated one vertex, so the user cannot even derive the clearance
distance.

The actual design file has
(net_name +12V) (xy 45.155104 -7.8994)
(net_name +5V)  (xy 45.002704 -7.8994)

so the +5V line is using the WRONG vertex information.

That _info_ does show (see other post around missing markers), on mouse
query,  so I think it is a simple Cut & paste typo bug, in the report
generator.
```
Original tags: drc

Story points: 6.0
PNS router doesn't take into account copper layers which have been removed from a PTH. (lp:#1618230)

[Original report](https://bugs.launchpad.net/bugs/1618230) created by **Simon Richter (sjr)**
```
When a via or thru-hole pad is placed, the inner layers will also receive
annular rings, even if there are no connections there. That makes it more
difficult to route signals between pins.

Ideally, only clearance from the drill hole would be required on these
layers.
```
Original tags: cern pcbnew pns

Story points: 68.0