giseldo/neodataset huggingface dataset:
Global module text visibility in pcbnew (lp:#1664761)

[Original report](https://bugs.launchpad.net/bugs/1664761) created by **Kristoffer (kristoffer-odmark)**
```
A global option to set the visibility of modules references or values is
lacking and would give better control of the silkscreen of the finished
PCB. Much the same way the global fields work.
```

Story points: 8.0
GAL hotkeys editor (lp:#1663896)

[Original report](https://bugs.launchpad.net/bugs/1663896) created by **John Beard (john-j-beard)**
```
The GAL tool system needs to be able to update the hotkeys via the hotkey
editors.

Currently, some GAL actions share hotkeys with legacy tools (and can be
updated in the editor), but many actions have no hotkeys.

The GAL canvas should be able to fill the editor with all registered
TOOL_ACTIONS and assign hotkeys to any of them.
```
Original tags: gal hotkeys missing-gal-tool

Story points: 14.0
Add shortcut for opening context menu in Eeshema (lp:#1663595)

[Original report](https://bugs.launchpad.net/bugs/1663595) created by **Mike Mitterer (reginaldbull)**
```
There is a shortcut for Mouse-Left-Click, Mouse-double-click but nothing to
get the context menu
```
Original tags: eeschema hotkeys

Story points: 14.0
when drawing track in hidden layer, layer does not become visible (lp:#1663556)

[Original report](https://bugs.launchpad.net/bugs/1663556) created by **simski (simski)**
```
kicad daily build from reynauld ppa

Application: kicad
Version: no-vcs-found-7592~57~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.13.0-105-generic x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.54.0
Curl: 7.35.0
KiCad - Compiler: GCC 4.8.4 with C++ ABI 1002
        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_SCH_IO_MANAGER=OFF
                  KICAD_USE_OCE=ON


when drawing a track on a hidden layer, the pads do show, but not the
tracks. nice behaviour would be to automagically show the hidden layer
```

Story points: 6.0
Select trace to next pad/via command (lp:#1662396)

[Original report](https://bugs.launchpad.net/bugs/1662396) created by **John Beard (john-j-beard)**
```
The GAL canvas already has some options for selecting bits of tracks/nets:

* Select "trival" connections
* Select connected-by-copper
* Select whole net

A useful addition would be "select to next pad/via" which selected all
segments up to the next pad or via. This would help when ripping up the
nearest piece of a track.
```
Original tags: gal pcbnew

Story points: 18.0
Wishlist: Unique zone "Clearance" for edge cuts (lp:#1662369)

[Original report](https://bugs.launchpad.net/bugs/1662369) created by **Evan Shultz (evan-shultz)**
```
I would like to have a unique clearance around zones to the board edge.
Currently, it appears the "Clearance" field applies to all copper elements
that the zone meets and the board edge.

For example, consider a zone on a high-voltage net. For 500V clearance, UL
60950 would require 1.6mm spacing and that is the value that I should put
into the Clearance field of the shape. I may want 1.6mm from this zone to
other copper, but if the product is in a plastic box with a single-sided
board it may be possible to run the zone right to the board edge. Pcbnew,
however, would still back off the board edge by 1.6mm which reduces my
usable routing area.

See the attached project for an example. The upper zone is priority 2 and
has 0.508mm clearance while the bottom zone is priority 1 and has 1.016mm
clearance. Both zones are backed off from the board edge by their clearance
value and the bottom zone, having a lower priority, backs off 1.016mm from
the upper zone. And also note that the net class for both zones' nets have
0.7mm spacing.

There are certainly hacks to get around this, but they're hacks. Since
board edge and copper-copper are, to me, distinct spacing requirements I
think they should be controlled separately.

I could be misusing Pcbnew or misunderstanding. If this can already be
handled, please forgive me and point me in the right direction. Thank you.


Application: kicad
Version: 4.0.5 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: clearance edge pcbnew zones

Story points: 30.0
Page settings and title block info not stored in wks files. (lp:#1662239)

[Original report](https://bugs.launchpad.net/bugs/1662239) created by **Eric Karr (erickarr)**
```
KiCAD Version: 4.0.5+dfsg1-4, release build
wxWidgets: 3.0.2 Unicode and Boost 1.62.0
Platform: Linux 4.9.0-1-686-page i686, 32 bit - Debian stretch

Issue:
When creating a default page template in Pl editor, none of the changes
made are saved. The following steps re-create the failure:

1) Open Pl editor
2) Open 'Page Settings' and change the default page size to US ledger (11 x
17)
3) Save the page layout design as "test.kicad_wks"
4) Close the Pl editor
5) Open the Pl editor
6) Open "test.kicad_wks"
7) Sheet is back to default settings..

I've noticed this happens on company name as well, I'm not sure if it
actually saves any of the settings. Do not hesitate to contact me if any
further information is required.

I also found a report of the same bug from 2014, and it was apparently
fixed, but I believe it's been reintroduced:

https://bugs.launchpad.net/kicad/+bug/1405887

Thanks,
Eric
```
Original tags: pleditor

Story points: 10.0
Ability to specify number and width of thermal relief spokes (lp:#1661963)

[Original report](https://bugs.launchpad.net/bugs/1661963) created by **efa (efa)**
```
KiCAD 4.0.5
Settings for thermal reliefs are:
- spoke width (Thermal relief width in Footprint Editor, Pad properties)
- antipad clearance (Thermal relief gap in Footprint Editor, Pad properties
so this is spoke lenght)
but the number of spokes is fixed to 4.

RFE: please add number of spokes settings, at least 2
```
Original tags: wishlist

Story points: 14.0
Grid dots too small on high DPI displays (Eeschema) (lp:#1660560)

[Original report](https://bugs.launchpad.net/bugs/1660560) created by **Robert Nicoll (virtual81)**
```
When using Eeschema on a Notebook PC a 14" 1440p (QHD) display the dots
that make up the grid are unable to be seen with the naked eye at ordinary
sitting distance.
When peering up close to the screen the green dots are visible.

Solutions could be to increase dot size, or make dots black, thus using all
3 (RGB) sub pixels.

Also mentioned in the forum by davidsrsb...
"High DPI displays are also the root cause of the hard to see unrouted
connection lines in OpenGL canvas.
This will be an increasing problem as pixel size continues to shrink"

I'm new to KiCad thus am not familiar with this issue, but suspect it too
to be relevant, and suspect i may come across it when the time comes.

Also a fair point made re pixel sizes shrinking, something that will need
to be catered for in future.

Version Info...
Application: kicad
Version: 4.0.5 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 8 (build 9200), 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 grid hdpi

Story points: 24.0
cant draw certain layers in footprint editor (lp:#1660549)

[Original report](https://bugs.launchpad.net/bugs/1660549) created by **Nicholas Savenlid (nicholas-z)**
```
can no longer draw a Dwgs.User line directly in footprint editor

need to draw silkscreen then change property.

see attached picture

Application: kicad
Version: (2017-01-29 revision 75ffcbc)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.51.0 OpenSSL/1.0.2j zlib/1.2.8 libssh2/1.8.0
nghttp2/1.16.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.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.62.0
Curl: 7.51.0
KiCad - Compiler: GCC 6.3.0 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
                  KICAD_SCRIPTING_ACTION_MENU=OFF
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_SCH_IO_MANAGER=OFF
                  KICAD_USE_OCE=ON
```

Story points: 6.0
Make it more obvious that you can type units into many textCtrls (lp:#1660156)

[Original report](https://bugs.launchpad.net/bugs/1660156) created by **Chris Pavlina (pavlina-chris)**
```
Many text fields in pcbnew allow the user to type a unit - for example [1].
The interface does nothing to make this clear, however. We should come up
with a way to make clear to the user that the unit is available for
editing.

Proposal: instead of having the unit outside the field, put it *in* the
unit, and autoselect just the number when the dialog is opened. If the user
accidentally deletes the unit from the field, default to the currently
selected unit as we already do.

Reference: https://bugs.launchpad.net/kicad/+bug/1660150

[1] https://misc.c4757p.com/unit-in-field.png
```
Original tags: pcbnew ui

Story points: 18.0
pcbnew: positioning of components in relation to already positioned ones (lp:#1660154)

[Original report](https://bugs.launchpad.net/bugs/1660154) created by **Adam (arudzins)**
```
It is possible "manually", thanks to the ability to set a zero for relative
position. But is a "manual labor", it can require to change the grid, if a
component is off the current grid. For larger boards this can be really
cumbersome.

I suggest to add an option similar to "move exactly", the name could be
like "place exactly relative to".

Also, it would be great to have in the context menu options to copy x or y
coordinate of another component (not necessarily, or rather: not only a
footprint), to facilitate positioning components in line.
```

Story points: 16.0
pcbnew: selection of size for tracks and vias (lp:#1660150)

[Original report](https://bugs.launchpad.net/bugs/1660150) created by **Adam (arudzins)**
```
Somehow it is just the way, that it is convenient to use millimeters for
defining vias and mills (or inches) for defining tracks. It is common to
use a few different sizes for both.

The only reasonable way of changing their size I know is to press Q in
OpenGL mode while routing. It would be great, but it requires to cycle
through units all the time.

I suggest to make the units in that size selection dialog independent of
the units selected for the main view (which are useful for measuring,
placement etc., and generally are defined once for a design, or perhaps
even for a designer).

I think that the simplest and the best solution is to provide two text
inputs for each size in the dialog, one for input in inches (or mills) and
the second for input in millimetres (when the user inputs a value into one
of them, the value in the second one gets updated accordingly).

Alternatively, this dialog could contain two dropdowns, one for selection
of units for tracks and the another for vias.
```

Story points: 6.0
pcbnew: margin for subtraction of soldermask from silkscreen (lp:#1660148)

[Original report](https://bugs.launchpad.net/bugs/1660148) created by **Adam (arudzins)**
```
This option is included for generation of gerbers and that's where it
should be. But the silkscreen is removed only from the soldermask openings,
while a bigger margin may be required. This additional margin could be
configured in the same dialog or, preferably, it could be defined per-pad
basis, just as we can configure a custom soldermask opening per pad. So my
recommendation is to add a "silk to soldermask clearance" property for
pads.

Currently, the not so convenient "volatile" workaround is:
- generate all gerbers,
- save the design, preferably not forgetting to make a backup,
- redefine soldermask openings of all pads in question (not forgetting
about any of them),
- generate silkscreen gerbers with silk-soldermask subtraction,
- do not save the design in the above two steps!
- recover the saved design.
```
Original tags: pcbnew

Story points: 10.0
Wish: use fp filter list in symbol properties footprint selector (lp:#1660131)

[Original report](https://bugs.launchpad.net/bugs/1660131) created by **Chris Pavlina (pavlina-chris)**
```
The footprint selector (not cvpcb, the one that appears when editing a
single part's Footprint field) should offer to filter footprints according
to that part's filter list.
```
Original tags: eeschema

Story points: 10.0
Warn about single pad nets in Eeschema (lp:#1660120)

[Original report](https://bugs.launchpad.net/bugs/1660120) created by **Adam (arudzins)**
```
KiCAD has no usable mechanism for warning the user against single pad nets.

For example, if I made a mistake in the schematics and swapped two letters
in a label, it is likely that I would found this out when the manufactured
PCB doesn't work as it was supposed to.

During netlist import pcbnew informs about deleting single pad nets, but
for a large PCB (where the problem is likely), if you even know this,
this is easy to overlook, inconvenient and thus unreliable..

Right now I use an external program to parse the netlist and check
for single pad nets.

Probably the easiest solution would be to have eeschema open a window
displaying the labels of all the single pad nets with a label. To be
less annoying, this window could have a checkbox not to be displayed again
for this schematics. In the netlist generation dialog there could also be
an associated checkbox telling to show this warning.
```
Original tags: eeschema erc

Story points: 20.0
drawing lines in footprint editor creates 0-length segments (lp:#1659500)

[Original report](https://bugs.launchpad.net/bugs/1659500) created by **Nicholas Savenlid (nicholas-z)**
```
When drawing poly-lines in footprint editor the end of lines often creates
extra unwanted dots (short lines)

often = almost always, it would be super easy to show this with a video.
fab-layer as an example

this is a new thing after the locking of drawings lines into certain
angles.

hmmm, i think i understand now that i should escape out of line drawing
instead of double-clicking to terminate the line.

but also draging en end of a line to resize/reposition it has become almost
impossible, often the whole windows starts to pan-around.


Application: kicad
Version: (2017-01-19 revision ba9576b)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.51.0 OpenSSL/1.0.2j zlib/1.2.8 libssh2/1.8.0
nghttp2/1.16.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.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.62.0
Curl: 7.51.0
KiCad - Compiler: GCC 6.3.0 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=OFF
                  KICAD_USE_OCE=ON
```

Story points: 8.0
Keyboard shortcut to toggle the "Limit tracks to 45 degrees" constraint (lp:#1659396)

[Original report](https://bugs.launchpad.net/bugs/1659396) created by **László Monda (mondalaci)**
```
I'm working on a design which mostly features components rotated in 90
degree increments, but some components are rotated in odd degrees. For the
latter components, it's very useful to disable the "Limit tracks to 45
degrees" constraint when routing tracks near them.

Given the above, I often find myself toggling the 45 degrees constraint. I
have always go to General Settings, then toggle the relevant checkbox which
is extremely counter-productive.

Being able to toggle this option via a shortcut key would result in a huge
productivity boost, and it would be very much appreciated.
```
Original tags: feature.request pcbnew

Story points: 16.0
Differential pair tuning claims different lengths before and after tuning (lp:#1656950)

[Original report](https://bugs.launchpad.net/bugs/1656950) created by **Kyle Owen (drovak-deactivatedaccount)**
```
I am tuning a differential pair, matching the length to a manually-set
value. Upon tuning the untuned trace, it turns green when it's added enough
meanders, and I click the left mouse button to accept it. Upon clicking it
again to confirm the tuned length, it says it's too short, even though it
was exactly correct, supposedly, in the previous tuning step. Now that it
claims it's too short by less than 1 mm, it's impossible to match exactly
with the desired settings. What should I believe? This seems to happen on
nearly all of my tuned traces.

Application: kicad
Version: 4.0.5 release build
wxWidgets: Version 3.0.2 (debug,UTF-8,compiler with C++ ABI 1002,GCC
4.2.1,STL containers,compatible with 2.8)
Platform: Mac OS X (Darwin 13.4.0 x86_64), 64 bit, Little endian, wxMac
Boost version: 1.57.0
         USE_WX_GRAPHICS_CONTEXT=ON
         USE_WX_OVERLAY=ON
         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 pns

Story points: 10.0
Allow to export the positions of through-hole components (lp:#1656688)

[Original report](https://bugs.launchpad.net/bugs/1656688) created by **László Monda (mondalaci)**
```
Our contract manufacturer has recently asked me to provide a file
containing the positions of every SMD and PTH component.

Normally, only the positions of SMD components are needed for pick and
place machines, but this time they're about program their automatic optical
inspection machine which also needs the positions of PTH components.

I'm aware of the Through hole, Surface mount, and Virtual placement options
of components, and I'd like to use them the right way. However, when
exporting a .pos file it doesn't seem to be possible to export PTH
components. Given the above use case, a checkbox to export the PTH
components too would be much appreciated.
```
Original tags: export

Story points: 10.0
Strings aren't quoted in pcbnew (lp:#1655193)

[Original report](https://bugs.launchpad.net/bugs/1655193) created by **Ed Johns (ejohns)**
```
Application: pcbnew
Version: 4.0.5 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 8 (build 9200), 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

Noticed this when using git and pcbnew. Not sure if it is a bug or
wishlist.

I set the date field to $Format:%cd$ so that when I archive from a
repository, it will expand the string to the release date.  Git expands the
string to a date with spaces.  These fields aren't quoted in the file
because there are no spaces as saved.  When I try to open the file in
pcbnew, there is a parse error.

I was able to workaround by adding a trailing space to force quotation, but
that may be unreliable if pcbnew ever removes trailing white-space.

I love working with the software, and like I said, there is a workaround,
so do with this what you will.

Thanks.

-Ed
```

Story points: 14.0
Touchpad pan 'choppy' in Eeschema, 'smooth' in Pcbnew (lp:#1654886)

[Original report](https://bugs.launchpad.net/bugs/1654886) created by **robotarmy (ry-white)**
```
Just as it says on the tin... I'm trying the latest release with the 'Use
touchpad to pan' option enabled on my mac. It works beautifully compared to
previous, but the schematic view is much choppier than the PCB layout view.

I'm guessing there's some "The schematic thing uses a different rendering
engine to the PCB thing" reason for it.

See here for example: https://youtu.be/w7z8w0Uyw_U

Application: kicad
Version: 4.0.5 release build
wxWidgets: Version 3.0.2 (debug,UTF-8,compiler with C++ ABI 1002,GCC
4.2.1,STL containers,compatible with 2.8)
Platform: Mac OS X (Darwin 14.5.0 x86_64), 64 bit, Little endian, wxMac
Boost version: 1.57.0
         USE_WX_GRAPHICS_CONTEXT=ON
         USE_WX_OVERLAY=ON
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON
```

Story points: 6.0
Different design rules for different areas of the board. (lp:#1654571)

[Original report](https://bugs.launchpad.net/bugs/1654571) created by **Ondrej Ille (illeondrej)**
```
Hi,

I was recently routing complex CPU board with DDR3. Routing out DDR3
signals under the BGA
and out of the BGA requires different minimal distances between the tracks.
It would
be really good to have zone DRC feature which would allow override default
DRC rules by
zone specific ones for either all signals or some signal groups.

A very close issue to this issue is that once the signals are routed with
e.g. 0.1 mm
distance, then DRC minimal value is changed to e.g. 0.3 mm, it is
impossible to route
the signals further (the actual ending distance must be increased manually
and route only then).
Also if two signals corrupt DRC minimal distance at any previous point the
Shove tool
does not work on further segments of these signals.

Ondrej Ille
```
Original tags: drc feature.request pcbnew

Story points: 20.0
Square pad DRC clearance not correct on corners (lp:#1652081)

[Original report](https://bugs.launchpad.net/bugs/1652081) created by **Nik (nikbowdler)**
```
Application: pcbnew
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

Pad clearance on square pads shows square outline, whereas corners should
show a radiused clearance, as copper fill correctly does. Routing of tracks
is prevented over the square corner area (with design rules enforced).
```
Original tags: clearance drc pad pcb

Story points: 8.0