giseldo/neodataset huggingface dataset:
BOM feature does not work in Windows7x64 (lp:#1751200)

[Original report](https://bugs.launchpad.net/bugs/1751200) created by **Hale Hale (hale-jp)**
```
In WIndows 7 x64, freshly installed KiCad 4.0.7 is incapable of creating a
BOM using any of the included .py scripts.

Example:
The eeschema circuit was checked by rules bug checker.
Here is the error report from bom_csv_grouped_by_value script; other .py
scripts give similar result:

Run command:
python "C:/Program
Files/KiCad/bin/scripting/plugins/bom_csv_grouped_by_value.py"
"C:/Users/user/Documents/KiCAD_project/amp.xml"
"C:/Users/user/Documents/KiCAD_project/amp"

Command error. Return code 1

Error messages:
Traceback (most recent call last):
  File "C:/Program
Files/KiCad/bin/scripting/plugins/bom_csv_grouped_by_value.py", line 67, in
<module>
    components = net.getInterestingComponents()
  File "C:/Program
Files/KiCad/bin/scripting/plugins/kicad_netlist_reader.py", line 624, in
getInterestingComponents
    ret.sort(key=lambda g: f(g.getRef()))
  File "C:/Program
Files/KiCad/bin/scripting/plugins/kicad_netlist_reader.py", line 624, in
<lambda>
    ret.sort(key=lambda g: f(g.getRef()))
  File "C:/Program
Files/KiCad/bin/scripting/plugins/kicad_netlist_reader.py", line 623, in f
    return re.sub(r'([A-z]+)[0-9]+', r'\1', v) + '%08i' %
int(re.sub(r'[A-z]+([0-9]+)', r'\1', v))
ValueError: invalid literal for int() with base 10: '1,2'
```
Original tags: bom eeschema python windows

Story points: 6.0
Hard coded hotkeys prevent user hotkeys from working (lp:#1751183)

[Original report](https://bugs.launchpad.net/bugs/1751183) created by **hauptmech (hauptmech)**
```
There were a number of features that had hotkeys hardcoded during the
initial testing phase. It would be super awesome if these were removed, or
moved to configurable hotkeys.

Hardcoded hotkeys prevent users from using the same key for another
function.


I've been away from the code a while but I believe the following are at
least some of the offending hardcoded hotkeys. (git commit
afd47100455961b0908bb5de6a5db9b0173ce936)

 E:\temp\kicad-source-mirror-master\common\tool\common_tools.cpp (1 hit)
        Line 37:         AS_GLOBAL, MD_CTRL + MD_SHIFT + 'X',
  E:\temp\kicad-source-mirror-master\Documentation\development\tool-
framework.md (4 hits)
        Line 297:             AS_GLOBAL, MD_CTRL + MD_SHIFT + int( 'L' ),
        Line 302:             AS_GLOBAL, MD_CTRL + MD_SHIFT + int( 'C' ),
        Line 396:             AS_GLOBAL, MD_CTRL + MD_SHIFT + int( 'L' ),
        Line 401:             AS_GLOBAL, MD_CTRL + MD_SHIFT + int( 'C' ),
  E:\temp\kicad-source-mirror-master\gerbview\tools\selection_tool.cpp (1
hit)
        Line 73:         AS_GLOBAL, MD_CTRL + MD_SHIFT + 'M',
  E:\temp\kicad-source-mirror-master\pcbnew\router\router_tool.cpp (4 hits)
        Line 87:         AS_GLOBAL, '6',
        Line 102:         AS_GLOBAL, '7',
        Line 106:         AS_GLOBAL, '8',
        Line 110:         AS_GLOBAL, '9',
  E:\temp\kicad-source-mirror-master\pcbnew\tools\edit_tool.cpp (4 hits)
        Line 123:         AS_GLOBAL, MD_SHIFT + 'R',
        Line 169:         AS_GLOBAL, MD_CTRL + MD_SHIFT + 'M',
        Line 174:         AS_GLOBAL, MD_CTRL + int( 'C' ),
        Line 179:         AS_GLOBAL, MD_CTRL + int( 'X' ),
  E:\temp\kicad-source-mirror-master\pcbnew\tools\pcbnew_control.cpp (3
hits)
        Line 112:         AS_GLOBAL, '>',
        Line 116:         AS_GLOBAL, '<',
        Line 242:         AS_GLOBAL, MD_CTRL + int( 'V' ),
  E:\temp\kicad-source-mirror-master\qa\common\mocks.cpp (1 hit)
        Line 315:         AS_GLOBAL, MD_SHIFT + 'R',


AS_CONTEXT hotkeys should also be checked.
```

Story points: 6.0
Inconsistencies on how fabrication settings are saved in PCBNew (lp:#1751171)

[Original report](https://bugs.launchpad.net/bugs/1751171) created by **José I. Romero (jose-cyborg)**
```
Some settings for generating PCB fabrication files are stored in the board
file (Like the layer selection and settings for the Gerber export) while
others (like the .drl and .pos file options) get saved to the global KiCad
settings. It means that when I have two projects that require different
settings for the drill file I need to remember to change them back and
forth (which gets old fast).

In an ideal world KiCad would allow saving and loading CAM files with all
the settings required (for say each fab house). But having everything in
the board file would be second best.
```
Original tags: pcbnew settings

Story points: 26.0
Pcbnew doesn't like 2 zone fill operations at once (lp:#1751112)

[Original report](https://bugs.launchpad.net/bugs/1751112) created by **Jeff Young (jeyjey)**
```
Open DRC and start a DRC with the "Fill zones first" checkbox selected.

While the zone fill progress dialog is up click back in the PCB window and
do a 'b'.

Pcbnew hangs.
```

Story points: 6.0
Footprint progress dialog shown when not necessary (lp:#1750858)

[Original report](https://bugs.launchpad.net/bugs/1750858) created by **Wayne Stambaugh (stambaughw)**
```
The footprint progress dialog is shown even when a footprint is selected
using the footprint viewer which should not happen.  To duplicate this bug:

1. Open Pcbnew.
2. Select the place footprint tool and click to add a new footprint.
3. Click the "Select by Browser" button in the "Load Footprint" dialog.
4. Select any library and footprint and click the "Insert footprint in
board" button.

Before the footprint is loaded and attached to the cursor, the footprint
library load progress dialog is shown and you have to wait until it is
complete (all footprint libraries are loaded) before you can place the
footprint.  Loading all of the footprints here is unnecessary as you
already have a library nickname and footprint name selected in the
footprint viewer and only need to load the selected footprint.  This
behavior was introduced by the addition of the progress dialog to the
footprint loading code.

Application: kicad
Version: (5.0-dev-4115-gdd04bcbcb), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.57.0 OpenSSL/1.0.2n (WinSSL) zlib/1.2.11 libidn2/2.0.4
libssh2/1.8.0 nghttp2/1.29.0
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.57.0
    Compiler: GCC 7.3.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
```

Story points: 6.0
ERC doesn't flag unnannotated "phantom" sheet V5 (lp:#1750620)

[Original report](https://bugs.launchpad.net/bugs/1750620) created by **Brian Piccioni (br0an)**
```
I don’t know if this is a bug but it is somehow “not right”

eeSchema error check does not flag unannotated reference designations in a
“phantom” second instantiation of a sheet.

In this project: https://github.com/OLIMEX/DIY-
LAPTOP/tree/master/HARDWARE/A64-TERES/TERES-PCB1-A64-MAIN_Rev_C

LCD.sch is only present in 1 copy on the main sheet (zoom out: they are
below the bottom of the sheet).

In the file there appears to be 2 instantiations:

$Comp
L TERES:RCLAMP0524P U?
U 1 1 57E655B9
P 12050 2500
AR Path="/56344A84/57E655B9" Ref="U?"  Part="1"
AR Path="/57E60F97/57E655B9" Ref="U15"  Part="1"
F 0 "U15" H 11870 2770 50  0000 L BNN
F 1 "RCLAMP0524P(SLP2510P8)" H 11700 2200 30  0000 L BNN
F 2 "OLIMEX_Devices-FP:SLP2510P8" H 12080 2650 20  0001 C CNN
F 3 "" H 12050 2500 60  0000 C CNN
        1    12050 2500
        1    0    0    -1
$EndComp

Note the U?, meaning there was no annotation. Running electrical rules
check on the schematic shows no errors associated with no annotation (I get
6 warnings and 1 error not related to the lack of annotation).
I have no idea how this second instantiation happened – it does not appear
to be in the PCB file – but essentially the lcd.sch file is corrupt and not
flagged as such.


Application: kicad
Version: (2018-02-09 revision 07fff6ed3)-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 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: eeschema erc

Story points: 6.0
pcbnew: area zone fill mode selection buttons stuck (lp:#1750494)

[Original report](https://bugs.launchpad.net/bugs/1750494) created by **Piotr Esden-Tempski (esden)**
```
After enabling the zone area fill display it is impossible to disable the
display using the toolbar buttons on the left side of eeschema.

It is possible to enable the zone area fill display but disabling it again
using either the "Do not show filled areas in zones" or the "Show outlines
of filled areas only in zones" buttons is impossible. It is still possible
to disable the display of the polygon fills via the menu options
"View"->"Drawing Mode"->"Wireframe Zones" and "View"->"Drawing
Mode"->"Sketch Zones".

This bug is reproducible on Ubuntu Xenial using "Gnome Flashback
(Metacity)" and "Gnome Flashback (Compiz)" the issue is not present when
using "Ubuntu Default". Also this behavior is not observable in i3
according to nickoe.

The issue was introduced in 3b085f0 "Pcbnew new menubar structure" commit.

Here is a video showing the observed behavior:
https://www.youtube.com/watch?v=220Jd_UkY-U
```
Original tags: gnome pcbnew

Story points: 8.0
Crash when duplicating custom pad shape primitives (lp:#1750463)

[Original report](https://bugs.launchpad.net/bugs/1750463) created by **Andrzej Wolski (awolski)**
```
Use board from attachment.
Duplicate custom pad primitive on pad 5.
Rotation: 20
Duplicate count: 10
Click on primitives list - pcbnew crashes.

Application: pcbnew
Version: (5.0-dev-4088-g5c6b19c55), 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: pcbnew

Story points: 6.0
Eeschema duplicate block: Source disappears (lp:#1750436)

[Original report](https://bugs.launchpad.net/bugs/1750436) created by **Bernhard Stegmaier (stegmaier)**
```
Mark a block in eeschema and choose "Duplicate block" from context menu.
The original marked block disappears, only the new duplicate is drawn and
follows mouse.
Looks like the block should be moved instead of a new block being created.
After the (new) block is placed, the source is visible again.

Expected:
Original source stays visible since this is not "move block".

Note:
When only selecting and moving a block, the old/original block stays
visible.
Behaviour seems to be swapped between move and duplicate.
Might be only a macOS issue.


Version:
<<<
Application: kicad
Version: (2018-02-08 revision 54ce01f8d)-master, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
Platform: Mac OS X (Darwin 17.4.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.59.0
    Curl: 7.55.1
    Compiler: Clang 9.0.0 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=OFF
    KICAD_SCRIPTING_MODULES=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=OFF
>>>
```
Original tags: eeschema

Story points: 6.0
cannot start routing inside cooper pour keepout (lp:#1750339)

[Original report](https://bugs.launchpad.net/bugs/1750339) created by **Chris Hinger (chrisqwertz)**
```
I have a keepout placed which only has the "no copper pour" option checked.
However, I'm not allowed to start a track in the keepout zone no matter
what routing options I try ("Allow DRC violations" & "Highlight
collisions".


Version Info:

Application: kicad
Version: (5.0-dev-4069-g322ce84fb), 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
```

Story points: 6.0
Create new component from old not available (lp:#1750303)

[Original report](https://bugs.launchpad.net/bugs/1750303) created by **William Hanna (william-hanna)**
```
The "create new component from old" button is no longer available in the
component editor. It is no longer possible to use an old component to
create a new one. You can "duplicate" a component, but this doesn't allow
you to create a name. There is no "edit" option for the component name
either which would allow the duplicate to be renamed to suit.

Application: kicad
Version: no-vcs-found-104b606~61~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-112-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
```

Story points: 6.0
MacOS App icons haven't been updated (lp:#1750284)

[Original report](https://bugs.launchpad.net/bugs/1750284) created by **Michael Kavanagh (michaelkavanagh)**
```
macOS running 20180218 nightly.
Application: kicad
Version: (5.0-dev-4069-g322ce84), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
Platform: Mac OS X (Darwin 17.4.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (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: macos packaging

Story points: 6.0
Crash unarchiving project after deleting contents (lp:#1749955)

[Original report](https://bugs.launchpad.net/bugs/1749955) created by **Jeff Young (jeyjey)**
```
Bug report courtesy of Clemens Koller:

Some more KiCad-from-scratch testing on Arch Linux:

Setup:
KiCad Version: (2018-02-16 revision 3c9a5b096)-master, release build
There is an previously archived project in some working directory
.../test9/test9.zip next to the project files test9.pro
(as well as an empty schematics and layout, ...)

How to reproduce:
- KiCad: Open Project -> ...test9/test9.pro.
- Filemanager: delete all files of the project except the previously
archived test9/test9.zip
- KiCad: When KiCad comes to front, the project tree gets reduced to
test9.pro (some refresh on focus? ok, cool).
- KiCad: When hitting Refresh, the project tree shows an additional "Empty
project" branch below test9.pro (different refresh?, well, ok).
- KiCad: File -> Unarchive Project -> select test9.zip -> Open -> Target
Directory -> test9 (keep current) -> Open -> Crash :-(


[13603.796230] kicad[14646]: segfault at 10 ip 00005647994c4655 sp
00007ffc39fea080 error 4 in kicad[56479942b000+16e000]

Is there a bug report filed already?
More debug information needed? (debug build just up)
```

Story points: 6.0
Highlight doesn't work properly when selecting a symbol in EEschema (lp:#1749799)

[Original report](https://bugs.launchpad.net/bugs/1749799) created by **Art (diametrix)**
```
With dual monitor setup when I select a symbol in EEschema, the view in
PCBnew recenter and zooms on the proper footprint but it doesn't highlight
until I move mouse cursor over the PCBnew window.  Previously highlight
worked immediately, as soon as a symbol is selected.

Application: kicad
Version: (2018-02-14 revision 6afdf1cf8)-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 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
```

Story points: 8.0
Wish: version specific configuration folder (lp:#1749659)

[Original report](https://bugs.launchpad.net/bugs/1749659) created by **Mitja Nemec (mitjan)**
```
Would it be possible for future Kicad releases to store configuration data
in version specific configuration folder (at least major version).

Currently the data is stored in
Windows: APPDATA\Kicad\ (e.g. C:\Users\{username}\AppData\Roaming\Kicad\)
Linux: ~/.config/Kicad/
MacOs: ~/Library/Preferences/Kicad/ (if comments in kicadpcb.cpp are
correct but I am not really sure)

If the data for V5 would be stored in :
Windows: APPDATA\Kicad\V5\ (e.g.
C:\Users\{username}\AppData\Roaming\Kicad\V5\)
Linux: ~/.config/Kicad/V5/
MacOs: ~/Library/Preferences/Kicad/V5/

user could have different versions installed concurrently. Though this is a
feature that should be
thought out. I don't see a problem with my workflow and until the nightlies
introduced eeschema library changes, I did run 4.0.7 and a nightly
successfully. But I suspect that different workflows, library and library
setups can break things. Maybe just implement the solution but require that
only one installation is supported.

Thanks for all the hard work.
```

Story points: 14.0
Copy and paste does not work for text with non ASCII characters (lp:#1749549)

[Original report](https://bugs.launchpad.net/bugs/1749549) created by **Andrzej Wolski (awolski)**
```
Paste does not work when copied objects contain text (applies to both
graphic text and footprint text) with non ASCII characters, for example
"Ø".

To reproduce this, just place text "Ø" and try to copy and paste this.


Application: pcbnew
Version: (2018-02-13 revision ac9fc949b)-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 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
```

Story points: 8.0
Kicad lacks a physical design language (lp:#1749474)

[Original report](https://bugs.launchpad.net/bugs/1749474) created by **jt_eaton (z3qmtr45)**
```
Kicad lacks a physical design language needed to pass engineering notes
from the schematic to the layout program.

A component and netlist does not contain enough information to design
anything but the simplest PCB. Trace and placement requirements are usually
listed in engineering notes that must be manually transferred and
implemented.

Kicad needs to define a way to enter this information in such a way that it
can be used by the pcb program .
```
Original tags: feature.request

Story points: 22.0
Edit Symbol Fields - Multiple Issues (lp:#1749287)

[Original report](https://bugs.launchpad.net/bugs/1749287) created by **Art (diametrix)**
```
Tried to use symbol table for the first time to assign values to the
components in the schematic.  Figured I would share my unbiased
observation.

Ok the problems:

1. Clicking on a cell highlights the whole row.  Ok, not sure what is the
point of it, but I guess somebody thought it might be useful.  Double click
the cell I want to edit - nothing happens.  Weird.  After literally a
minute of clicking on cells, I finally figured out that you need to click
ones to highlight a row, and then click ones again on a cell in the raw to
enable editing.  0_0 There is The International Obfuscated C Code Contest,
there should be a category there for a GUI design, this interface would
definitely score there!

2. Now that I enabled editing of the cell, enter data and click on the row
below to enter the data.  The data is entered in the cell below the cell I
was editing. O_O

3 There are two description columns in my table.  I had to add a custom
Description field, because I needed to have part description accessible
when I edit symbol in the schematic.  So one of those description fields
can't be edited at all (which partially contributed to the extended time of
trying to figure out how to edit cells in the problem  #1)

4. It takes a while to arrange all the columns for more or less civilized
editing (adjusting width of columns, disabling the one's that don't need to
be showing etc.)  Then if you exit the table and then enter again, all that
editing is lost and you have to start from scratch.

I personally would expect for the table to mimic Excel behavior for editing
and saving data.  But maybe it is just me?
```
Original tags: eeschema

Story points: 32.0