sand1024

@dxli Well, in my last pull request I've addressed this issue - by adding several ways for rendering arcs as well as options for that. in 2.2.2 version - that's...

@TiuMui Please check whether in latest 2.2.2 alpha. It should be fixed now - it if is so, please close the ticket.

@dxli Oh, ok - yet probably it's better to have separate issue that is specific to elliptic arcs to avoid confusions?

@dxli It seems that the issues is still not fixed. Now after your fixes (commit 960acbbdee6a47314ea9f23f0d8a5947c68620f5 at 22/08/2025) from the situation seems to be even worse than before: if there...

@dxli I see - so it's good that you're aware of it. What concerns me with all that clipping-related algorithm is proper support of UCSs and, more specifically, the situation...

@dxli and a couple of generic notes (not truly related to the previous comment): `The performance issue is there because we need to render within 1 pixel even after zoomed...

@dxli `find intersections between the entity the viewport border, if there's intersection, but no visible segment found, generate an error. This appears to be the bug behavior here. ` However,...

@city-1921 No, it is seems it is known issue and I suppose it should be fixed in 2.2.1.3RC and 2.2.2-alpha (https://github.com/LibreCAD/LibreCAD/releases/tag/2.2.2_alpha-latest)

@Questions2000 I suspect this behaviour is related to specific window manager... I can't reproduce it according to steps you've described, yet I've checked under Win10 - probably it's Debian specific?

@Questions2000 Oh, that's a good point. yes, it seems you're right and there is a small shift. Ok, I'll take a look.