Bug 365478 - Eraser switch size lag
Summary: Eraser switch size lag
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Brush engines (show other bugs)
Version: 3.0
Platform: Other Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-12 16:19 UTC by Zafio
Modified: 2018-07-31 13:38 UTC (History)
4 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Zafio 2016-07-12 16:19:50 UTC 
When "eraser switch size" is active, there is a lag of 1 or 2 seconds when switching to erase mode.

Reproducible: Always

Steps to Reproduce:
1. Enable "eraser switch size" at brush settings
2. Use the shortcut to switch to eraser mode
3.


Expected Results:  
No delay.
Comment 1 wolthera 2016-07-12 17:50:19 UTC 
This should get fixed once we move over to VC 1.2

Don't recall if there was a duplicate yet...
Comment 2 Halla Rempt 2016-08-15 14:03:53 UTC 
Can you check whether http://files.kde.org/krita/3/windows/devbuilds/krita-3.0.1-alpha2.zip fixes the issue? That's the first Vc 1.2-enabled build.
Comment 3 Denis Moon 2016-08-22 17:29:56 UTC 
I confirm this too. Not fixed in the second alpha. At the moment, I'm experiencing the bug on Windows 10 only. KDE Plasma works fine.
Comment 4 Halla Rempt 2016-11-01 12:06:12 UTC 
With the latest beta (http://download.kde.org/unstable/krita/3.0.91/) on Windows 10, I cannot reproduce this issue. We did fix a slowdown in brush engine settings for this release, so that might have been related. If you can still reproduce with the latest beta, please notify me.
Comment 5 Julian Steinmann 2018-07-31 09:55:07 UTC 
I am not able to reproduce this issue with Krita 4.1.1 running KDE Neon. @Zafio, does the problem persist for you or can you confirm that this bug is fixed?
Comment 6 Zafio 2018-07-31 13:14:49 UTC 
(In reply to Julian Schraner from comment #5)

Hi Julian, this one is fixed!