Bug 387699 - Horizontal mirror sometimes put the stroke farther from the axis than needed
Summary: Horizontal mirror sometimes put the stroke farther from the axis than needed
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.3.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-12-08 03:21 UTC by Rupert Alves Stapf
Modified: 2018-10-29 01:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Picture of bug (124.79 KB, image/png)
2017-12-08 03:21 UTC, Rupert Alves Stapf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rupert Alves Stapf 2017-12-08 03:21:14 UTC
Created attachment 109252 [details]
Picture of bug

When using the horizontal mirror tool with the free hand brush tool, sometimes the strokes weren't showing. After checking the preview of the layer I found out that some strokes were being positioned in a wrong position in relation to the axis.

In the attached picture you can see in the preview that a circle that should be on the shoulder of the character appears much farther to the left side of the preview.

This happened several times already.

Every time I was using a Wacom intuos draw tablet (don't know if the same issue happens with mouse or other inputs).
Comment 1 Halla Rempt 2018-01-03 15:38:04 UTC
Did you scale your image before this happened?
Comment 2 Rupert Alves Stapf 2018-01-03 15:48:18 UTC
(In reply to Boudewijn Rempt from comment #1)
> Did you scale your image before this happened?

No scaling was performed before this happened.
Sometimes it happened just after creating a new canvas and starting drawing.

One thing that I noticed is that there was a newer version of Krita available when I reported this. With the new version (I'm using 3.3.2 now) this problem hasn't happened up until now.

Perhaps it was fixed or there was another change that was performed and influenced on this issue.

Since I don't know if it really was something that was fixed willingly or was just something that happened by chance, I think it would be nice to understand what caused this to be able to avoid the same kind of issue in future releases, however it is not impacting my drawings right now (because I stopped using the version with this issue).
Comment 3 Halla Rempt 2018-01-03 22:09:29 UTC
Hm.... Best also test the latest nightly builds: https://binary-factory.kde.org/job/Krita_Nightly_Build/ -- we didn't do any intentional coding in this area, but stuff always is interconnected!
Comment 4 Andrew Crouthamel 2018-09-28 03:40:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-29 01:59:04 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!