Bug 393345 - Stabilizer preview circle inaccurate while using windowed mode for multiple views.
Summary: Stabilizer preview circle inaccurate while using windowed mode for multiple v...
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Brush engines (other bugs)
Version First Reported In: 4.0.1
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: investigated, needs_verification, triaged
Depends on:
Blocks:
 
Reported: 2018-04-20 15:30 UTC by Dustin Mundy
Modified: 2018-09-19 14:33 UTC (History)
2 users (show)

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

Attachments
screenshot (98.57 KB, image/png)
2018-09-01 12:07 UTC, Halla Rempt 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Dustin Mundy 2018-04-20 15:30:16 UTC 
When using multiple views of the same file (windowed mode) the stabilizer preview circle sometimes gets confused. I believe it's working as intended but showing a much larger circle than normal.

https://i.imgur.com/46SJqnN.png
Comment 1 Halla Rempt 2018-09-01 12:07:19 UTC 
Created attachment 114733 [details]
screenshot

Added the screenshot to the bug report
Comment 2 Emmet O'Neill 2018-09-16 05:25:22 UTC 
I wasn't able to confirm this bug. It seems to me that the Brush Stablizer's 'delay' parameter exists per view, and when I click from one view winder to the other the value and radius change accordingly. 

Dustin, do you see the value 'delay' value changing as you click from one view to the other?

If that's not the issue you're having, could you please give us more information about the exact steps that I can use to reproduce this bug in a new file?

Thanks for the bug report, please let us know if you have a way to reproduce this bug.
Comment 3 Andrew Crouthamel 2018-09-19 14:33:43 UTC 
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.