eeschema: wrong placing of symbol fields

Bug #1665718 reported by Eldar Khayrullin
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Medium
jean-pierre charras

Bug Description

Eeschema do incorrect place of common fields.
See images.

Application: kicad
Version: no-vcs-found-7663~57~ubuntu16.10.1, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.50.1 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.33 librtmp/2.3
Platform: Linux 4.8.0-37-generic x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.61.0
Curl: 7.50.1
KiCad - Compiler: GCC 6.2.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_OCE=ON

Tags: eeschema
Revision history for this message
Eldar Khayrullin (eldar) wrote :
Revision history for this message
Eldar Khayrullin (eldar) wrote :
Revision history for this message
Eldar Khayrullin (eldar) wrote :
Revision history for this message
Eldar Khayrullin (eldar) wrote :
Revision history for this message
Andrey Kuznetsov (kandrey89) wrote :

This needs to be fixed, otherwise eeschema is impossible to use if all the common fields are scattered half a page away from the placed component.
Still present in the latest nightly.

Revision history for this message
Chris Pavlina (pavlina-chris) wrote :

I'm marking this confirmed as several people have reported this now - yet I still remain unable to reproduce it myself :\

Changed in kicad:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
metacollin (metacollin) wrote :

I am effected by this bug, its been present for quite some time, so many commits, including the most recent, are effected. I am using the macOS version.

It only occurs when autoplace is turned off. If it is on, its ok.

I've attached a copy of the part seen in the screenshot, and a screen shot of the issue.

Screenshot can be found here: https://metacollin.com/screens/upshot_2CNVX5wp.png

Revision history for this message
Chris Pavlina (pavlina-chris) wrote :

Okay, with the attached library I absolutely can reproduce this.

Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

Fixed in revision 28a6ca1e23904b080ef34cf9bc1fed91d2191cc9
https://git.launchpad.net/kicad/patch/?id=28a6ca1e23904b080ef34cf9bc1fed91d2191cc9

Changed in kicad:
status: Confirmed → Fix Committed
assignee: nobody → jean-pierre charras (jp-charras)
Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.