Black border using SkiaSharp canvas integration about questpdf HOT 4 CLOSED

Hairlines 😄

This looks like a bug on the ScottPlot end (though it is an amazing library!). I would suggest clearing the space with just:

canvas.Clear(SKColors.Transparent);

However, this workaround works as expected:

.SkiaSharpCanvas((canvas, size) => {
    canvas.ClipRect(new SKRect(1, 1, size.Width - 1, size.Height - 1)); // here
    canvas.Clear();
    canvas.Clear(SKColors.White);
});

from questpdf.

Hairlines 😄

This looks like a bug on the ScottPlot end (though it is an amazing library!). I would suggest clearing the space with just:

canvas.Clear(SKColors.Transparent);

However, this workaround works as expected:

.SkiaSharpCanvas((canvas, size) => {
    canvas.ClipRect(new SKRect(1, 1, size.Width - 1, size.Height - 1)); // here
    canvas.Clear();
    canvas.Clear(SKColors.White);
});

Thank you for the quick reply!

Unfortunately, your suggested change results in the following SVG and does not work either:

<?xml version="1.0" encoding="utf-8" ?>
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="536" height="357">
	<clipPath id="cl_8">
		<rect x="1" y="1" width="533.40002" height="354.93335"/>
	</clipPath>
	<g clip-path="url(#cl_8)">
		<rect width="536" height="357"/>
		<rect fill="white" width="536" height="357"/>
	</g>
</svg>

Any clues on where the issue lies?

EDIT:
Pardon me for my very limited SVG knowledge. I originally thought the rectangles were being drawn separately from the clip path, but upon looking into it more, it seems that the g element references the correct clip path and it should theoretically work. Still, I see the frame in the resulting PDF.

from questpdf.

It really looks like a ScottPlot problem. I've managed to spot the hairlines viewing the SVG with InkScape's inkview, too. Therefore it seems like it's not a QuestPDF bug and I'll try to discuss this further at ScottPlot's GitHub.

from questpdf.

It really looks like a ScottPlot problem.

I wouldn't say it's ScottPlot problem per se. It is very close to how Skia converts drawing instructions to SVG content. Then, about how is that content rendered in non-native resolutions (where points do not match integer pixels). I needed to try hard to see this issue on my 4k screen.

But taking into account that ScottPlot officially supports SVG, they can make this small improvement.

from questpdf.