tiar
August 25, 2021, 11:10am
2
I can confirm and I know why it happens from the code
@tiar are you talking about this?
Finally, I wasn’t able to wait this week-end to test…
So, first, I was wrong: file /krita/plugins/assistants/Assistants/kis_assistant_tool.cc define class to manage assistants, so, useless to solve my my problem…
Looking on other files, I found this in (most of) project() method implemented on assistants classes:
(Example from /krita/plugins/assistants/Assistants/VanishingPointAssistant.cc)
qreal dx = pt.x() - strokeBegin.x();
qreal dy = pt.y() - strokeBegin.y();
if (dx * dx + d…
Grum999
@AhabGreybeard
Can’t really test/check for now but the problem is not related to this one?
@Grum999 I’ve just tried the appimage and the ‘delay’ that I see is 4px of image size at 2048 x 2048 and 4096 x 4096 predefined templates no matter what the zoom setting. These two templates are 100dpi.
With a 2028 x 2048 image at 600dpi, the delay is 18 px.
With the A4 600dpi, it’s also 18px.
At 1200 dpi, it’s 36px.
At 50 dpi it’s 2px.
At 10dpi it’s 1px.
The dx and dy seem to be physical image distances.
I mean, by changing document dpi to 1 for example, problem is still here?
Grum999
Oh good grief
I’ll wipe my original topic and get back to the OP of the bug report.
@Grum999 Good catch
it takes the first four pixels (no idea why 4 pixels in the canvas space and not (maybe?) display) to calculate the direction. And it only remembers the first point. Which results in a straight line when it finally decides which assistan to follow 
it needs reworking of the system.
That one had totally faded from my mind.