eeschema - 'symbol fields'-editor - linebreak in a component field makes schematic unreadable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Fix Released
|
High
|
Jeff Young |
Bug Description
When working with the new 'symbol fields'-editor in eeschema, I've experienced a breakage of the associated .sch-file due to linebreaks appearing on one of the component-fields.
I'm not exactly sure from where these linebreaks appear, but they somehow make their way into the fields when copying component field-data from one part to another. Somehow selecting a field graphically and copy-pasting it to another sometimes selects a hidden linebreak, which then partially breaks the associated .sch file. Could also be, that the linebreak originates from an external source, like the part# from mouser.com.
Anyways, since these linebreaks can be so disastrous, I thought some added resilience to how fields are managed would be neat. I.e., when linebreak is encountered on a component field, it could be filtered out before saving the .sch or something. I can't imagine a case, when linebreak is actually wanted on a component field.
I added a screenshot on how the error-messages might look like when trying to open up a broken schematic.
## VERSION INFO ##
Application: Eeschema
Version: 5.1.4-e60b266~
Libraries:
wxWidgets 3.0.4
libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-60-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
wxWidgets: 3.0.4 (wchar_t,wx containers,
Boost: 1.65.1
OpenCASCADE Community Edition: 6.9.1
Curl: 7.58.0
Compiler: GCC 7.4.0 with C++ ABI 1011
Build settings:
USE_
USE_
KICAD_
KICAD_
KICAD_
KICAD_
KICAD_
KICAD_
BUILD_
KICAD_
KICAD_
KICAD_SPICE=ON
Changed in kicad: | |
assignee: | nobody → Jeff Young (jeyjey) |
status: | New → In Progress |
Changed in kicad: | |
milestone: | none → 5.1.5 |
importance: | Undecided → High |
Changed in kicad: | |
status: | Fix Committed → Fix Released |
Here's how a broken line looks like ( line 1307 )