[SOLVED] SVG import with holes

tormyvancool · February 16, 2022, 9:12pm

I use the 6.0.1 and it’s now the 6.0.2

Please where can I find the changelog?
I would like to read which issues where addressed

EDIT 15 04 2022: Thanks to the developers that with the release 6.0.4 they solved this issue forever

maykol_rey · February 16, 2022, 9:22pm

these are the changes of 6.0.2

marekr · February 17, 2022, 3:51am

Well, technically not that page but this one

tormyvancool · February 20, 2022, 10:53pm

Ok I notice they didn’t addressed the issue with the SVG at all. It still there since one year and more.

gkeeth · February 22, 2022, 1:57pm

the issue you reference is listed as fixed in (upcoming) v7 and (upcoming) 6.0.3.

tormyvancool · February 22, 2022, 11:40pm

Ok I can’t wait for it

albin · February 23, 2022, 7:40am

Then don’t. It should be included in the testing builds by now. 6.0.x testing build for windows can be found here: Downloads | KiCad EDA

eelik · February 23, 2022, 7:47am

You can already have it, go to Downloads | KiCad EDA and download the latest testing…exe installer. It includes all bugfixes after 6.0.2. It’s theoretically possible that there are some new bugs introduced by the fixes, but usually it’s safe, and they need testing anyway. It replaces the 6.0.2 installation.

EDIT: dang, I was distracted while writing and albin was faster…

tormyvancool · February 23, 2022, 11:09pm

Right, although I do use to get only the official releases rather than nightbuilds.

eelik · February 23, 2022, 11:46pm

Remember that “nightly” builds are different from “testing” builds. The former are unstable development builds.

The latter are stable daily builds for the stable version bugfixes, and only bugfixes. They are more bug free than the latest released stable version. It just has happened a couple of times that a new bug has been introduced with a bugfix. But that’s rare.

tormyvancool · February 24, 2022, 1:39pm

I’m downloading it

EDIT … nice Thanks Chrome.
The way to turn around is to open the download folder and double click up there. THEN it works

tormyvancool · February 24, 2022, 1:49pm

Well I don’t know what they solved, but I see it is not solved at all. Lookthatt P … which is not a font, but a SVG “P” made with curved lines, then the hollow is subtracted. It works fine on any application but KiCAD… This issue is not addressed

Not only, I imported (erroneously) the color version. PCBNew crashed.

gkeeth · February 24, 2022, 2:06pm

@tormyvancool it would be good if you attached the two SVGs you referenced to your issue (the one with the cutout that isn’t removed, and the one that crashes)

tormyvancool · February 24, 2022, 2:12pm

Please her the file. I have modified it since it’s a logo of a Customer.

KiCAD_NO_HOLLOW

der.ule · February 24, 2022, 2:13pm

Just for info, here is the SVG commit:

nice to see that you are helping by testing this particular feature, don’t forget to give some kind of feedback to the developers.

tormyvancool · February 24, 2022, 2:17pm

Thank you for the link. I posted up there too.

Then not clue on when it will be ready this. To me is vital since I have logos to import, and the PNG to Vectorial that’s in KiCAD is simply horrible.

craftyjon · February 24, 2022, 2:36pm

This attitude is not very helpful. It appears as though you found an edge case that was not solved by the original commits, although those did solve other problems. So, the issue was addressed for many cases, but not yours. I recommend being more polite when encountering bugs in KiCad.

Your logos can be imported using the bitmap converter already. Of course we will try to improve the SVG importing in KiCad, but you are coming across as demanding that KiCad support this because it is “vital” to you. Remember that for the most part, KiCad is developed by volunteers, and unless you pay for bug fixes directly, complaining about something “still being broken” is not going to come across well to those volunteers.

tormyvancool · February 24, 2022, 2:41pm

craftyjon:

tormyvancool:

Well I don’t know what they solved, but I see it is not solved at all.

This attitude is not very helpful. It appears as though you found an edge case that was not solved by the original commits, although those did solve other problems. So, the issue was addressed for many cases, but not yours. I recommend being more polite when encountering bugs in KiCad.

tormyvancool:

To me is vital since I have logos to import, and the PNG to Vectorial that’s in KiCAD is simply horrible.

Your logos can be imported using the bitmap converter already. Of course we will try to improve the SVG importing in KiCad, but you are coming across as demanding that KiCad support this because it is “vital” to you. Remember that for the most part, KiCad is developed by volunteers, and unless you pay for bug fixes directly, complaining about something “still being broken” is not going to come across well to those volunteers.

It has nothing to do with politeness.
If a case was not addressed, it isn’t. What should I say then?
The facts are there. This issue is not solved.

About the bitmap converter, I already said that’s horrible the final result it returns.
Hence I’m very reluctant to use it.

albin · February 24, 2022, 2:44pm

Although it doesn’t hurt to be polite about it, does it?

FYI, I just tested with your SVG and I can confirm that it doesn’t work for me either. The SVG you uploaded opens fine in InkScape, Chrome, Edge and LibreOffice Draw, but in KiCad 6.0.2-98 the hole in the P is filled.

Application: KiCad (64-bit)

Version: (6.0.2-98-g5cc2bef954), release build

Libraries:
wxWidgets 3.1.5
libcurl/7.78.0-DEV Schannel zlib/1.2.11

Platform: Windows 10 (build 19042), 64-bit edition, 64 bit, Little endian, wxMSW

Build Info:
Date: Feb 22 2022 22:10:06
wxWidgets: 3.1.5 (wchar_t,wx containers)
Boost: 1.76.0
OCC: 7.6.0
Curl: 7.78.0-DEV
ngspice: 36
Compiler: Visual C++ 1928 without C++ ABI

Build settings:
KICAD_USE_OCC=ON
KICAD_SPICE=ON

craftyjon · February 24, 2022, 2:46pm

Actually, it does a lot. None of the KiCad developers are obligated to help solve your problems, and if you are rude, it is less likely that anyone will want to.

Report that you have an SVG that still doesn’t import correctly, attach the SVG, and wait for someone to investigate it. There are multiple different reasons that an SVG might not be imported correctly, so saying “the issue is not solved” is not accurate: some issues were already solved, but you have found a different issue with similar symptoms.

Again, this is unhelpful and also impolite. You could be more constructive here by posting an issue showing the image you’re trying to convert, the bitmap converter results, and why you are not satisfied with the results.