giseldo/neodataset huggingface dataset:
Design Rule Check changes layout (recalculates filled areas)  (lp:#1721547)

[Original report](https://bugs.launchpad.net/bugs/1721547) created by **Fabian Binz (fbinz)**
```
Hi,

running the Design Rule Check should not change the layout of your board.
Currently, as part of running the Pcbnew's DRC, the filled areas are
recalculated.
If, due to some previous routing, there are overlaps with filled areas, it
can lead to the situation displayed in the attached project.
Here, one trace overlaps a filled area.
Now, when running the DRC, this overlap is removed by recalculating the
filled areas.
However, the DRC doesn't mention this in any way, so one can easily
believe, that the design prior to executing the DRC was correct (and thus
leads to ordering wrong layouts…).

In my opinion this is a user interface bug. I understand, that it might be
necessary to recalculate the filled areas during the DRC. However, *if*
this leads to changes, it should be clearly presented to the user. Maybe
something similar to the way in which the user gets asked, if the
annotations should be automatically updated, when she tries to export a
netlist and some parts are not annotated.

Application: kicad
Version: 4.0.5+dfsg1-4 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: Linux 4.9.0-3-amd64 x86_64, 64 bit, Little endian, wxGTK
Boost version: 1.62.0
libcurl version: 7.52.1 (with SSL - GnuTLS/3.5.8)
         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: 4.0.5 drc

Story points: 8.0
spice netlist with ? ? ? when unconnected pins (lp:#1720619)

[Original report](https://bugs.launchpad.net/bugs/1720619) created by **laurent (laurent2)**
```
In SPICE netlist, all different nets should have a different name.
But when a integrated U1 has unconnected pins, they are all netlisted with
a question mark :
XU1  VCC 1 ? ? ? /INPUT /uCtoLED GND PIC12C508A
whatever options are used to generate the spice netlist.

Solution : new net number should be generated for the unconnected nets when
generating a spice netlist.

Another trick : I am not sure, but mot probably the / before the net name
shoud be also removed as some simulator may refuse to run because of them.

Thank you,
Laurent
```
Original tags: eeschema spice

Story points: 6.0
DRC does not connect tracks that pass through pads rather than ending on them (lp:#1718831)

[Original report](https://bugs.launchpad.net/bugs/1718831) created by **Strntydog (strntydog)**
```
Tracks which intersect with pads (but do not terminate at the anchor point
of the pad) are listed as unconnected.

This is wrong from a physical model of the board, the Copper features
overlap, and so they are "electrically" connected, and DRC should report
them as such.

It is also inconsistent with DRC violations, which do obey copper
connectivity, a track crossing a pad of another net, at any point will
issue a DRC violation when checked.

There is an edge case where a track only slightly touches a pad, and is
electrically connected, but Not connected sufficiently for the design,
but that is not the same thing as being "unconnected" and isn't handled
by DRC now in any event.

There may be a requirement to report tracks which touch pads, but do not
terminate on the anchor point of the pad, but that is a different
requirement, and not the same as a track being unconnected.

Version:
```
Application: kicad
Version: no-vcs-found-e2505cb~60~ubuntu17.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) librtmp/2.3
Platform: Linux 4.10.0-33-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```
```
Original tags: drc pcbnew

Story points: 46.0
Via Tool should honour DRC (lp:#1718827)

[Original report](https://bugs.launchpad.net/bugs/1718827) created by **Strntydog (strntydog)**
```
With DRC checking enabled, it shouldn't be possible to drop a via using the
Via Tool, if
that via would cause a design violation.

Exactly like its not possible to lay two tracks with different nets over
one another.

Example:
two tracks on different layers, with different nets.  It should not be
possible to put a via over them where they intersect, because thats a
design violation.

Version:
Application: kicad
Version: no-vcs-found-e2505cb~60~ubuntu17.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) librtmp/2.3
Platform: Linux 4.10.0-33-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON
```
Original tags: gal pcbnew pns

Story points: 26.0
Enhancement - 3D models can't be referenced by relative path from footprint (lp:#1717735)

[Original report](https://bugs.launchpad.net/bugs/1717735) created by **Roger Clark (rogerclarkmelbourne)**
```
Currently if a custom library footprint has a 3D model, there is no way to
use a relative path from the footprint (pretty) file to the WRL file.

The only workarounds seem to be by either placing the custom 3D model in
with the master 3D files (  KISYS3DMOD ) (not ideal on Windows since this
requests admin to copy the file), or to copy the file into the Project
folder and use  KISYSPROJ  in the footprint 3D model location field

Neither of these options is particularly good, for the portability of 3D
models with custom libs.


I'm not sure of a good solution. Perhaps allowing relative paths for the
model file location e.g. ../3DModels/mymodel.wrl

PS. I have tried using ./mymodel.wrl and ../3DModels/mymodel.wrl and
neither seems to work when I try to look at the model via on the PCB when
in PCBNew
```
Original tags: 3d-viewer pcbnew

Story points: 30.0
Eschema font rendering is hard to read (lp:#1716695)

[Original report](https://bugs.launchpad.net/bugs/1716695) created by **kuro68k (kuro68k)**
```
Version: 4.0.7, Windows 7 x64

Font rendering in Eschema schematics is quite hard to read, especially when
zoomed out but even with fairly large text sizes. See the attached
examples.

It would be nice if either a better rendering engine or at least some
hinting could be used to improve the appearance of text.
```

Story points: 10.0
Import of .dxf R14 (which is output by Inkscape) (lp:#1716310)

[Original report](https://bugs.launchpad.net/bugs/1716310) created by **swulf (swulf)**
```
Inkscape is a very useful tool for producing PCB outlines for insertion
into the Edge Cuts layer in pcbnew. However, KiCad cannot import the DXF
files Inkscape produces.

Because there are many DXF variants, it seems that it would be good if
KiCad could also support importing graphics in SVG format directly. This
would make the task of importing graphical elements such as complex board
outlines drawn in external packages very much easier.
```
Original tags: 4.0.7 dxf import pcbnew

Story points: 14.0
Dialogs do not appear on same monitor as app OSX (lp:#1715461)

[Original report](https://bugs.launchpad.net/bugs/1715461) created by **Richard Arens (gamplod)**
```
This happens for almost every dialog in every app in the Mac KiCad suite.
This is a huge problem when using multiple monitors.

Steps to reproduce:
1.) Open a schematic or pcb.
2.) Click on a component and press e to edit some value.
3.) Close the edit dialog.
4.) Move the app to another monitor.
5.) Click another component and press e.

The dialog opens on the previous monitor.  However it is invisible.  In
order to view the dialog you have to drag the app back to the previous
monitor, and the dialog appears as a small sliver on the side of the
screen.  This is not isolated to the edit dialog.

Can dialogs please open on the monitor that the app is running?

Other info:
I have "Group windows by application"  and "Displays have separate Spaces"
selected in Mission Control preferences.

Please help!  I love KiCad but this issue severely hinders my productivity.
```
Original tags: mac monitors osx

Story points: 20.0
Allow user to change grid size for the footprint preview in Eeschema. (lp:#1714771)

[Original report](https://bugs.launchpad.net/bugs/1714771) created by **firewalker (firew4lker)**
```
Now that someone can select a footprint for a component through Eeschema's
component properties dialog,  it would be helpful if the footprint preview
window allowed the user to change grid size.

Press "E" over a component, go to footprint field. Select "Browse
Footprints".

Application: kicad
Version: (2017-08-31 revision eec1366ea)-master, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.55.1 OpenSSL/1.1.0f zlib/1.2.11 libpsl/0.18.0 (+libicu/59.1)
libssh2/1.8.0 nghttp2/1.23.1
Platform: Linux 4.12.8-2-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.55.1
    KiCad compiler: GCC 7.1.1 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=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
```
Original tags: eeschema

Story points: 10.0
Need "modal dialog" in measure distance tool (lp:#1713932)

[Original report](https://bugs.launchpad.net/bugs/1713932) created by **Alessandro Fabilli (o-alessandro)**
```
When use the "measure distance" tool in PCBNEW, at the end of measurement,
when make the second click, not appear a modal dialog with the result.
You must read the measure beafore make second click. This is not friendly
to use.
The optimal is when you make a click at end point of measurement, to
displayed a modal dialog with the reault of the measurement (distance and
angle).

Thanks


Application: kicad
Version: (2017-08-23 revision 57619956e)-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), versione 64-bit, 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
    KiCad 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
```

Story points: 6.0
Visible indication in Plot / fab file generation that DRC is out-of-date (lp:#1712579)

[Original report](https://bugs.launchpad.net/bugs/1712579) created by **Julien Faucher (suzizecat)**
```
Hi !
I would like to request a feature : I think that a mechanism that would
check if a (ground) plane collide with a track which don't belong to that
plane would be quite useful.

The problem is the following. Imagine that you are designing your PCB. You
end it, DRC check it and take a well-deserved pause.
Some time later, you come back and make some pretty small arrangements in
the layout to make it cleaner (You just push/drag/shove a track) and leave
it for today.

The next day, you produce the Gerber files, send them and... Oh surprise !
Some tracks were fused with the ground plane... Happy track-cutting time :D

The problem is the use of the "Don't show filled area in zones" which is
damn convenient but allow some serious mistakes.

I think that a pop-up like "Would you like to recalculate the zone filling
before generating Gerber ?" or best :
"Warning, you got some tracks mixed up with some filling zones". could save
some lives...
or even running a DRC check before the generation (with, maybe) an option
to disable that in the general options

Thanks,
Julien FAUCHER
```
Original tags: drc export gui pcbnew

Story points: 42.0
PNS router length tuning does not match full length (inc. pad to die) (lp:#1711541)

[Original report](https://bugs.launchpad.net/bugs/1711541) created by **Andrey Fedorushkov (faa)**
```
PNS router length tuning - not check length pad in die

Tuning length single trace and diff trace not used length pad in die.
Tuner calculate length only on board.

Application: kicad
Version: no-vcs-found-(2017-aug-18 git:d25fdfdb8)-master, release build
Libraries: wxWidgets 3.0.3
           libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.7.0
nghttp2/1.9.2
Platform: Linux 4.9.40-desktop-1.mga6 x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.60.0
Curl: 7.54.1
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
                  KICAD_SCRIPTING_ACTION_MENU=OFF
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_OCE=OFF
```
Original tags: pcbnew pns

Story points: 24.0
Auxiliary window displayed off-screen on dual display system (lp:#1711222)

[Original report](https://bugs.launchpad.net/bugs/1711222) created by **Floyd Masukawa (loachman33)**
```
Auxiliary window displayed off-screen on dual display system

        ▪       Kicad app launched and display on one (left) display
        ▪       Moved main app window to second display (right)
        ▪       Launched “Schematic Library Editor” Window titled: “Part
Library Editor: no library selected”
        ▪       Button selected: “Library Browser”
        ▪       Launching window: “Library Browser [no library selected]”
        ▪       Button selected: “Select Library”
        ▪       Auxiliary window: “Select Library” not displayed
        ▪       Subsequent mouse clicks in Library Browser window generated
error beep
        ▪       Moving “Library Browser” window around eventually caused
“Select Library” to appear in opposite window but in a semi-transparent
state
        ▪       Continuing to move “Library Browser” window around
        ▪       got solid “Select Library” window
        ▪       normal function resumes


Application: kicad
Version: 4.0.6 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 16.7.0 x86_64), 64 bit, Little endian, wxMac
Boost version: 1.57.0
Curl version: libcurl/7.54.0 SecureTransport zlib/1.2.8
         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: dual-display dual-head ui

Story points: 10.0
kicad: Auxiliary window displayed off-screen on dual display  (lp:#1711219)

[Original report](https://bugs.launchpad.net/bugs/1711219) created by **Floyd Masukawa (loachman33)**
```
Auxiliary window displayed off-screen on dual display system

        ▪       Kicad app launched and display on one (left) display
        ▪       Moved main app window to second display (right)
        ▪       Launched “Schematic Library Editor” Window titled: “Part
Library Editor: no library selected”
        ▪       Button selected: “Library Browser”
        ▪       Launching window: “Library Browser [no library selected]”
        ▪       Button selected: “Select Library”
        ▪       Auxiliary window “Select Library” not displayed
        ▪       Subsequent mouse clicks in Library Browser window generated
error beep
        ▪       Moving “Library Browser” window around eventually caused
“Select Library” to appear in opposite window but in a semi-transparent
state
        ▪       Continuing to move “Library Browser” window around
        ▪       got solid “Select Library” window
        ▪       normal function resumes


Application: kicad
Version: 4.0.6 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 16.7.0 x86_64), 64 bit, Little endian, wxMac
Boost version: 1.57.0
Curl version: libcurl/7.54.0 SecureTransport zlib/1.2.8
         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: dual-head kicad

Story points: 10.0
3D view: zoom level changes when switching to/from orthographic projection (lp:#1710561)

[Original report](https://bugs.launchpad.net/bugs/1710561) created by **Oivind Toien (otoien)**
```
When a board is displayed in 3D view in the nightly build and switching
to/from orthographic projection, the zoom level changes by a factor of
about 2, opposed to the behavior in the stable 4.06 version which keeps
zoom level. Also in the nightly, 3D view  in the footprint browser keeps
zoom level when switching to/from orthographic projection as in the stable
version.

Application: kicad
Version: (2017-08-11 revision 356f607cd)-makepkg, release build
Libraries: wxWidgets 3.0.3
           libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0
nghttp2/1.23.1 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
- Build Info -
wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.64.0
Curl: 7.54.1
KiCad - Compiler: GCC 7.1.0 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
(also affects the 2017-08-13 nightly build)
```
Original tags: 3d-viewer pcbnew

Story points: 8.0
catching pad of anchor as moving reference (lp:#1710451)

[Original report](https://bugs.launchpad.net/bugs/1710451) created by **Novak Tamas (novak-7)**
```
The moving reference point can be a pad's center or the anchor of
footprint. When I click a pad, a Clarify dialog appears, but behaves
reversed: it moves anchor when pad is selected, and catches pad if
footprint selected. see video
```

Story points: 6.0
proper object selection in eeschema (lp:#1709999)

[Original report](https://bugs.launchpad.net/bugs/1709999) created by **Novak Tamas (novak-7)**
```
To harmonize pcbnew and eeschema, nothing should happen in eeschema when
selecting a block (with mouse held down, drag, released). Would need
pushing M to move. It may give the option I miss very much: adding/removing
object to/from selection with Shift/Ctrl + mouse clicks.
You usually need to move a "fuzzy" block: rectangle selection is quite
limited in use.

That works like that in pcbnew.
Immediate moving of block just selected when releasing mouse button at
selection, is rather unpleasant than a fine feature.
```

Story points: 16.0
3D export: include layers e.g. copper, soldermask, silkscreen etc.

[Original report](https://bugs.launchpad.net/bugs/1709793) created by **Nicholas Savenlid (nicholas-z)**
```
or any pads, or part-of-pcb info like silkscreen, vias, traces

It looks so good in t the viewer.

I wonder why this information is lost in step export ?

at least it doesn't show up when imported into Creo, i could try freecad
also.


Application: kicad
Version: (2017-04-25 revision 5013ea2e8)-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 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.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
```

Story points: 6.0
Python SetSelected() doesn't display until view switched (lp:#1709149)

[Original report](https://bugs.launchpad.net/bugs/1709149) created by **Greg Smith (gmsmith)**
```
Windows nightly as of July 31, 2017

Executing the following in Scripting Console:

import pcbnew

for m in pcbnew.GetBoard().GetModules():
        m.GetValue().SetSelected()
        m.GetReference().SetSelected()
        for d in m.GraphicalItems():
                d.SetSelected()

for d in pcbnew.GetBoard().GetDrawings():
        d.SetSelected()


The selected items do not appear in OpenGL view until the view is switch to
default and back.

Also, adding DRAWSEGMENTS on the board don't show up until the view is
switched.

This also happen in Linux and possibly MacOS and, to a limited extent, in
4.0.6 Stable.

Application: kicad
Version: (2017-07-31 revision 67ae5935d)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.54.0 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0
nghttp2/1.19.0 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.63.0
Curl: 7.54.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=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_OCE=ON
```
Original tags: pcbnew python

Story points: 26.0
Eeschema: Block sel: dont place after Rotate (lp:#1709069)

[Original report](https://bugs.launchpad.net/bugs/1709069) created by **Aurabindo J (jay-aurabind)**
```
In Eeschema, occasionally I have a block of components that I need to move,
as well as rotate. Now I do this with these many steps:

1. Block Select the components
2. Move it to a temp location
3. Rotate it there
4. Block select again and place it to target location

It would make it much easier if the Rotate operation in the Block
Selection's right click context menu would not place the components
immediately after a Rotate operation. Same goes with Pcbnew. This way, my
steps would be reduced to:

1. Block Select the compoents
2. Rotate and place it to target location
```

Story points: 10.0