Bug 395943

Summary:	Cintiq 27qhd stylus is not syncing up properly.
Product:	[Applications] krita	Reporter:	skudfargus
Component:	Usability	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	critical	CC:	ghevan, halla, hillionnora, liz.edminster
Priority:	NOR	Keywords:	usability
Version:	4.0.4
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
URL:	https://www.youtube.com/watch?v=mNNjfgKpuUY
Latest Commit:		Version Fixed In:

Description skudfargus 2018-06-28 02:32:47 UTC

Stylus cursor is not syncing properly.  There is noticeable offset gap from where the stylus is and where the cursor is being display on the screen. This problem is specific to Krita, it does not happen using any other paint programs.  It also only happens when using the style, a regular mouse works fine in Krita.  

I came across someone else having a similar problem as shared on reddit; however, none of their suggestions have solved the problem.
https://www.reddit.com/r/krita/comments/6y69j3/on_windows_10_dualmonitor_set_up_the_brush_is/

Comment 1 Halla Rempt 2018-06-28 08:17:10 UTC


*** This bug has been marked as a duplicate of bug 395679 ***

Comment 2 hillionnora 2019-04-13 20:21:46 UTC

when you zoom  a little with the stylus, the cursor remains stuck on the drawing and you have to restart the application

Comment 3 hillionnora 2019-04-13 20:23:30 UTC

When you zoom with the stylus , the cursor remains stuck on the drawing and you have to restart  the application

Comment 4 vanyossi 2019-04-14 04:32:20 UTC

The original report is about cursor offset using cintiq which was investigated in BUG 295679 and found as an upstream problem.

The cursor problem hillionnora@gmail.com is citing is another issue, which could or could not be reported already. Please, hillionnora, make a new report if it is not reported already for the "cursor bug" as it a completely different bug, avoid adding different issues on unrelated bugs and aldo avoid reopening already fixed bugs specially when the resolution is clear.

Closing again.

*** This bug has been marked as a duplicate of bug 395679 ***