[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2020-08-05 Thread Chris Jones
https://bugs.kde.org/show_bug.cgi?id=370237 --- Comment #18 from Chris Jones --- I can't notice the delay on the Surface Pro 4 now though. -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2020-08-05 Thread Chris Jones
https://bugs.kde.org/show_bug.cgi?id=370237 --- Comment #17 from Chris Jones --- (In reply to Bollebib from comment #16) > @chrisjones > > incidently is it possible this issue occurs after using undo? It happens regardless of whether there has been any undo. Also I noticed it starts

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2020-08-05 Thread Bollebib
https://bugs.kde.org/show_bug.cgi?id=370237 --- Comment #16 from Bollebib --- @chrisjones incidently is it possible this issue occurs after using undo? -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2020-08-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=370237 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2020-08-04 Thread Chris Jones
https://bugs.kde.org/show_bug.cgi?id=370237 --- Comment #14 from Chris Jones --- (In reply to Tymond from comment #13) > . I think this might be a different issue, since the pauses only occur at the start of new strokes rather than mid-stroke. Also it happens regardless of the amount of RAM

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2020-08-03 Thread Tymond
https://bugs.kde.org/show_bug.cgi?id=370237 Tymond changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|---

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2020-08-03 Thread Tymond
https://bugs.kde.org/show_bug.cgi?id=370237 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #12 from Tymond

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2018-10-28 Thread Chris Jones
https://bugs.kde.org/show_bug.cgi?id=370237 Chris Jones changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2018-10-27 Thread Andrew Crouthamel
https://bugs.kde.org/show_bug.cgi?id=370237 Andrew Crouthamel changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2018-09-27 Thread Andrew Crouthamel
https://bugs.kde.org/show_bug.cgi?id=370237 Andrew Crouthamel changed: What|Removed |Added Keywords||triaged --- Comment #9 from Andrew

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2017-11-23 Thread Chris Jones
https://bugs.kde.org/show_bug.cgi?id=370237 --- Comment #8 from Chris Jones --- Desktop: With OpenGL the problem is less pronounced than it used to be; the strokes are drawn in small chunks instead of fluidly with a timing of roughly 0.7 seconds between strokes, gets slightly

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2017-11-23 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=370237 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2017-09-06 Thread Isabelle LaBrot
https://bugs.kde.org/show_bug.cgi?id=370237 Isabelle LaBrot changed: What|Removed |Added CC|

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2016-10-09 Thread Chris Jones via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370237 --- Comment #6 from Chris Jones --- I forgot to add that this problem resurfaced in the first 3.1 beta (3.0.99.90), so I'm still using 3.0-9e17aff since that's the most recent build that doesn't exhibit the problem. I don't recall

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2016-10-08 Thread Chris Jones via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370237 --- Comment #5 from Chris Jones --- No stabilizer, only basic smoothing is on, although none of the smoothing options seem to make any difference. Also I haven't been able to repeat the Advanced Colour Selector incident so far. --

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2016-10-08 Thread Bollebib via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370237 Bollebib changed: What|Removed |Added CC||kwadraatn...@hotmail.com

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2016-10-07 Thread Boudewijn Rempt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370237 --- Comment #3 from Boudewijn Rempt --- Yes... Though it's still strange that this doesn't happen to me, but it suggests a place to start looking. -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2016-10-07 Thread Chris Jones via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370237 --- Comment #2 from Chris Jones --- Happens whether it's enabled or not. Strangely, I just opened the Advanced Colour Selector docker, and the problem went away until I closed it again. I tried opening it again and the problem was

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

2016-10-07 Thread Boudewijn Rempt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370237 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org ---