giseldo/neodataset huggingface dataset:
DXF import placement origin not respected in GAL (lp:#1708537)

[Original report](https://bugs.launchpad.net/bugs/1708537) created by **Nick Østergaard (nickoe)**
```
With GAL canvases the DXF placement origin options does not fully apply,
the object will be "attached" t the cursor instead of the specified origin
point.

I think this was a bugfix added recently in GAL, but I think one should
have that as a option in the dialog. Maybe call it "Place manually with
cursor" or something similar.

The origin setting is respected in legacy.


Application: pcbnew
Version: (2017-08-03 revision 3570154ef)-master, debug build
Libraries: wxWidgets 3.0.3
           libcurl/7.54.1 OpenSSL/1.1.0f zlib/1.2.11 libpsl/0.17.0
(+libicu/59.1) libssh2/1.8.0 nghttp2/1.23.1
Platform: Linux 4.11.6-3-ARCH x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.64.0
Curl: 7.54.1
KiCad - Compiler: GCC 7.1.1 with C++ ABI 1011
        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
```
Original tags: cern dxf gal import

Story points: 14.0
highlight collisions incorrectly snaps endpoint to collision boundary (lp:#1707105)

[Original report](https://bugs.launchpad.net/bugs/1707105) created by **hauptmech (hauptmech)**
```
When using GAL highlight collision mode, the trace endpoint is snapped to
the yellow octogon pad collision boundary rather than staying with the
cursor. This makes fine manual placement difficult.
```

Story points: 10.0
Dimension lines obscure value (lp:#1705431)

[Original report](https://bugs.launchpad.net/bugs/1705431) created by **Stephen (steejb)**
```
Very often, the lines extending from the two dimension end points run
through the text of the dimension, making it un-readable.



Application: pcbnew
Version: 4.0.6 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1010,GCC
6.3.0,wx containers,compatible with 2.8)
Platform: Windows 7 (build 7601, Service Pack 1), 32 bit, Little endian,
wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON
```
Original tags: pcbnew

Story points: 22.0
Pl_Editor spontaneously returns my page layout to default configuration! (lp:#1704253)

[Original report](https://bugs.launchpad.net/bugs/1704253) created by **Ryan (jensenr30)**
```
Pl_Editor returns my page layout to default after I delete all the parts of
it! This is not intuitive, and it does not seem right. This is a bug, plain
and simple.

Steps to reproduce bug:
open KiCad
Tools -> Run Page Layout Editor (Ctrl + Y)
delete all of the features of the page (right click on rect1, press the 'D'
key; right click on rect2, press the 'D' key; right click on segm1, press
the 'D' key; ...)
Once you have deleted them all, the page will return to the default state
(all of the features of the page will spontaneously return!!) But in the
left-hand window, none of the features are displayed at first: picture for
proof:
right before I delete the last part of the page: http://prntscr.com/fvgo23
(attachment 1)
right after  I delete the last part of the page: http://prntscr.com/fvgo7l
(attachment 2)

Now, if I right click on "<default>" and select "Add line":
http://prntscr.com/fvgoks (attachment 3)
All the features show up on the left-hand pane again:
http://prntscr.com/fvgopo (attachment 4)

What I think should happen is this: when I delete all the features of the
page, they STAY GONE. They should not reappear for no reason.


Thank you for taking the time to read my bug report  :)

Cheers!
Jensen


Application: pl_editor
Version: 4.0.6 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1010,GCC
6.3.0,wx containers,compatible with 2.8)
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON




Application: kicad
Version: 4.0.6 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1010,GCC
6.3.0,wx containers,compatible with 2.8)
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON
```

Story points: 6.0
eeschema: add distinction between "internally not connected" and "do not connect" pins (lp:#1703908)

[Original report](https://bugs.launchpad.net/bugs/1703908) created by **Timur Kristóf (venemo)**
```
Some components have pins that are "internally not connected", meaning that
you are free to connect whatever you want. However, some of them are "do
not connect", meaning that it is used by the developers of the component
and in your own circuit you should not use them.

Currently, eeschema only has a single "no connect" pin type, and doesn't
distinguish between the above two.
```
Original tags: eeschema feature.request

Story points: 34.0
eeschema ERC: "pin connected to some other pins but no pin to drive it" error is useless (lp:#1703905)

[Original report](https://bugs.launchpad.net/bugs/1703905) created by **Timur Kristóf (venemo)**
```
I have a lot of ERC errors like this:

ErrType(3): Pin connected to some others pins but no pin to drive it
    @ (133,35 mm,147,32 mm): Pin 4 (Power input) of component U4 is not
driven (Net 212).

However, this is not helpful, because the ERC's ability to reason about the
power inputs is limited:
- When you have a passive filter (eg. serial R) between the power input and
power output, ERC thinks that the power input is not powered. (This can be
"fixed" by littering the schematic with PWR_FLAG components, which is very
inconvenient.)
- When you drive a component from an MCU GPIO pin, it complains that the
power input is not powered, even though in reality the GPIO can source the
necessary current. (This cannot be fixed by a PWR_FLAG because that will
create yet another severity error.)

Also, this error message cannot be silenced, even though connecting power
inputs to bidirectional pins is allowed in the ERC settings. This results
in a lot of "noise", ie. useless error messages in ERC, and makes it hard
to notice real bugs.

I understand that it's impossible for the ERC to figure out whether my GPIO
can source enough current, and how the filter works. Suggestion: please add
an option to silence this warning.
```
Original tags: eeschema erc

Story points: 10.0
eeschema ERC: please persist settings in project (lp:#1703842)

[Original report](https://bugs.launchpad.net/bugs/1703842) created by **Timur Kristóf (venemo)**
```
Currently the ERC settings are not persisted at all: after a restart KiCAD
will forget ERC settings entirely.

For the correct behaviour I would expect the ERC settings to be persisted
in the project or the schematic file. Rationale: it makes sense that
different projects require individual sets of ERC rules.
```
Original tags: eeschema erc feature.request

Story points: 26.0
Cvpcb calculates number of pins wrong (lp:#1703155)

[Original report](https://bugs.launchpad.net/bugs/1703155) created by **Ryan (jensenr30)**
```
I am using a 74HC14 part (a simple and VERY common 14-pin logic gate).
This happens to be a hex schmitt-trigger-input inverter gate array.
I am only using 4 of the 6 logic gates from this chip. I am also using the
GND and VCC pins (pins 7 and 14 respectively).
There are only 4 logic gates on my schematic.
The total number of pins I am USING is 10.
When I run Cvpcb, it thinks that a 74HC14 is a 10-pin part, but that is
wrong.
A 74HC14 is a 14-pin part.
When I place two extra inverters from my 74hc14, Cvpcb then thinks that
this is a 14-pin (which is correct).

My problem is this: Cvpcb should think my 74HC14 is a 14-pin ALWAYS.
It shouldn't DECIDE how many pins it has based on how many gates I place on
my schematic.
Even if you are only using 1 of the 6 gates in the part, you still have to
place the entire part.


***

Application: kicad
Version: 4.0.6 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1010,GCC
6.3.0,wx containers,compatible with 2.8)
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON
```

Story points: 10.0
Spice netlist doubled device names (lp:#1700853)

[Original report](https://bugs.launchpad.net/bugs/1700853) created by **buleks (buleks)**
```
When i generate spice netlist using eeschema i get for each device
something like this:
rr4 vg2 net-_r4-pad2_ 10
rr5 net-_d3-pad1_ vg2 1k

Instead print r5 it repeat first letter.

It not occur in stable release.
I compile code form branch master.
Source revision:commit 4bdac4de705849777f5a59e0f6f7ee1dd6274a8c
```

Story points: 20.0
Pads joined in soldermask layer in gerber files (lp:#1698457)

[Original report](https://bugs.launchpad.net/bugs/1698457) created by **Emily Björk (bjoerk-emily)**
```
Application: pcbnew
Version: 4.0.6 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1010,GCC
6.3.0,wx containers,compatible with 2.8)
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON


Reproducible on platforms: Windows 10 and Gentoo Linux confirmed (Kicad
4.0.4).

Steps to reproduce:
1. Create new layout in Pcbnew.
2. Add housings TQFP32 7x7mm 0.8mm pitch footprint from the standard
library.
3. Rotate footprint by 45degrees
4. Set soldermask clearance to 0.05mm and minimum width to 0.15mm.
5. Plot to gerber.
6. Open the solder mask layer in gerber viewer.

Actual result: Several pads will have been joined in the soldermask layer.
Expected result: No pads are joined in the solder mask layer.

I believe that the issue is caused by a missing epsilon value when
computing the soldermask on a rotated component. It so happens that the
footprint has 0.55mm wide pads and 0.8mm pitch, if you add it up with the
clearance and minimum width you get: 0.8mm === 0.55mm + 2*0.05mm + 0.15mm
and I believe that it's a truncation error in the floating point math used
to compute the final solder mask.

For now I'm working around it by using 0.0499999 solder mask clearance.
```
Original tags: pcbnew

Story points: 22.0
GAL does not honor the auto delete old track setting (lp:#1696678)

[Original report](https://bugs.launchpad.net/bugs/1696678) created by **Nicholas Savenlid (nicholas-z)**
```
I have attached a video to explain this, but:

I want traces both to and bottom layer for current capacity

But once i add second layer the first trace is removed.

So.. adding the second trace on bottom removes the first trace on top and
vice verse.

Video attached
```
Original tags: cern gal missing-gal-tool pcbnew

Story points: 8.0
No-merge zones to allow different clearances, radii, etc. (lp:#1695761)

[Original report](https://bugs.launchpad.net/bugs/1695761) created by **Connor Crenshaw (connorgames-geek)**
```
When I attempt to create a copper zone with a different clearance parameter
inside of a larger zone, both zones are merged and the new, merged zone has
the clearance of the first one I put on the board. This behavior is
unintuitive and makes it (as far as I can see) impossible to have a
different clearance for part of a zone. The same behavior occurs if I try
to line up the edges of the zones instead of putting one inside of another.

I am running a self-build build of revision cf87536 on linux.
```
Original tags: pcbnew

Story points: 16.0
Startpoint and endpoint for drawing properties aren't user friendly (lp:#1694964)

[Original report](https://bugs.launchpad.net/bugs/1694964) created by **Nicholas Savenlid (nicholas-z)**
```
I file this wishlist here since the blueprint cannot attatch picture

and to descirbe in words would be complicated and lengthy

this is Line segments property dialog box from footprint editor.

pls see picture
```
Original tags: pcbnew ui

Story points: 10.0
footprint picker in eeschema should obey component footprint filter patterns (lp:#1692462)

[Original report](https://bugs.launchpad.net/bugs/1692462) created by **Lorenzo Marcantonio (l-marcantonio)**
```
When editing the footprint field in eeschema (not using the cvpcb button)
the footprint library browser doesn't use the footprint filter information
defined in the component. The cvpcb component list works correctly
```

Story points: 6.0
Scrollbar arrows not working in pcbnew GAL (lp:#1690780)

[Original report](https://bugs.launchpad.net/bugs/1690780) created by **der.ule (u-estrada)**
```
Application: kicad
Version: 4.0.6 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1010,GCC
6.3.0,wx containers,compatible with 2.8)
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON

Stepwise scrolling using the scrollbar's arrows of the GUI is not working,
clicking them has not effect.
```
Original tags: cern gal pcbnew

Story points: 24.0
Edit box loses focus when cursor enters 3D rendering (lp:#1690766)

[Original report](https://bugs.launchpad.net/bugs/1690766) created by **Cezary Zieliński (olek13)**
```
In the footprint editor Footprint Properties dialog box, "3d Settings" tab
has three edit boxes groups: Scale, Rotation and Offset. If the  mouse
pointer moves through the preview gadget, the text coursor in the edit box
disappears.

Application: kicad
Version: (2017-05-14 revision 14bb238b3)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.60.0
Curl: 7.52.1
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=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_OCE=ON
```
Original tags: 3d-viewer pcbnew

Story points: 10.0
Calling pcbnew.LoadBoard in python causes unhandled exception (lp:#1689976)

[Original report](https://bugs.launchpad.net/bugs/1689976) created by **Thomas Figueroa (tom-figueroa)**
```
 Application: kicad
Version: (2017-05-08 revision d4e41c4f9)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.53.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
Platform: Windows 10 (build 16188), 64-bit edition, 64 bit, Little endian,
wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.63.0
Curl: 7.53.1
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=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_OCE=ON

Any calls of pcbnew.LoadBoard in python result in an unhandled exception on
Windows. Tested with personal build as well as nightly KiCad server build.
```
Original tags: python windows

Story points: 8.0
eeschema and gerbview lack main menu and/or toolbar dropdown for grid selection (lp:#1689024)

[Original report](https://bugs.launchpad.net/bugs/1689024) created by **Jonas Stein (news-g)**
```
I suggest to add a drop down menu to select the current grid distance.
The selector should be on a prominent position in the GUI and always show
the current value.

The user can increase and decrease the selection with a hotkey.
```
Original tags: eeschema feature.request

Story points: 22.0
Feature request: Allow coloured global labels (lp:#1688924)

[Original report](https://bugs.launchpad.net/bugs/1688924) created by **Jonas Stein (news-g)**
```
The user should be able to select optionally a colour (RGB value?) to mark
global labels.

One can use this to mark groups, pairs, or functions (safety = yellow,
informative signal = blue, ...)
This is not to complicate and very useful for large plans with many labels.
```
Original tags: eeschema feature.request

Story points: 22.0
component table viewer - column width too large (lp:#1688650)

[Original report](https://bugs.launchpad.net/bugs/1688650) created by **michalstec (nnn4000)**
```
Columns widths depends of fields content. In some of cases, eg long
hyperlinks or grouped designators of decoupling capacitors (may be hundreds
of them), column may be many times wider than window on a screen. It would
be more convenient if columns widths were limited to some reasonable value
(like half or one third of screen width).


Version: 201705041117+4f2ed1b~58~ubuntu14.04.1 (from
https://code.launchpad.net/~js-reynaud/+archive/ubuntu/ppa-kicad)


Application: kicad
Version: no-vcs-found-4f2ed1b~58~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)
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=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_OCE=ON
```

Story points: 6.0
Backspace and delete buttons don't work properly for deleting tracks (lp:#1688074)

[Original report](https://bugs.launchpad.net/bugs/1688074) created by **Art (diametrix)**
```
Not so long ago a very useful feature was implemented which enables
deleting tracks while in the track drawing mode.  While in track drawing
mode you push delete to delete a track segment and backspace to delete the
whole track up to the nearest pad or via (there was a separate bug report
here https://bugs.launchpad.net/kicad/+bug/1490958)  Unfortunately it is
still not working properly.  If the track is within another footprint
extents or next to another footprint, pressing DEL or Backspace deletes the
track segment or the whole track (which is correct behavior) but at the
same time it deletes the footprint as well (which is not suppose to happen)
If you hit undo you can reverse deleting the footprint while the track
remains deleted.  So you can eventually get the the desired result, it just
takes several steps.

Application: kicad
Version: (2017-04-26 revision ade263f30)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.60.0
Curl: 7.52.1
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=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_OCE=ON
```
Original tags: gal pcbnew pns

Story points: 46.0
Eeschema: interrupted lines in some zoomlevels (lp:#1687491)

[Original report](https://bugs.launchpad.net/bugs/1687491) created by **Jonas Stein (news-g)**
```
reproduce: In kicad 4.0.5 and 4.0.6 draw a circuit and zoom in and out a
few times.
Only a few zoomlevels have this glitch. It seems not to be in the data.
```
Original tags: eeschema glitch

Story points: 6.0
No sketch mode text rendering in GAL (lp:#1687483)

[Original report](https://bugs.launchpad.net/bugs/1687483) created by **Andrzej Wolski (awolski)**
```
Text in both OpenGL and Cairo modes is always displayed in filled mode,
regardless of "show in sketch mode" settings.

Version: (2017-04-21 revision 0e6723bb1)-makepkg, release build
```
Original tags: gal pcbnew

Story points: 6.0
pcbnew: "Auto delete old track" not working (lp:#1686939)

[Original report](https://bugs.launchpad.net/bugs/1686939) created by **Xiguang Wang (kurapica)**
```
Whenever "Disable auto delete new track" button is toggled, I cannot have 2
tracks from pin A to pin B at the same tim

Application: kicad
Version: 4.0.6 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1010,GCC
6.3.0,wx containers,compatible with 2.8)
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON
```
Original tags: cern gal pns

Story points: 8.0
Feature Request: Fast switch schematic/pcb view (lp:#1686010)

[Original report](https://bugs.launchpad.net/bugs/1686010) created by **Nicola Lunghi (nicola.lunghi)**
```
Hi
I very like an option/button/keyboard shortcut to fast switch between
schematic view and pcb view

eagle have alt + 1 to go to schematic view and alt + 2 to go to the pcb (or
create it if its not there)

Best Regards
Nicola Lunghi
```
Original tags: starter ui

Story points: 10.0