Bug 361457 - [TRUST] No pressure detection with trust tablet
Summary: [TRUST] No pressure detection with trust tablet
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (other bugs)
Version First Reported In: 2.9.11
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-06 15:06 UTC by Bruno Santos
Modified: 2018-06-11 04:35 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Santos 2016-04-06 15:06:47 UTC
Well, the tablet used to crash Krita (like in ll the other reports about krita and trust), but i've changed to version 2.9 an now it doesn't crash, but has no pressure either.

Reproducible: Always

Steps to Reproduce:
1.Launch Krita
2.Try drawing with any tool that uses pressure.
3.Bingo!

Actual Results:  
... the program fails to detect variation in pressure.

Expected Results:  
Should have pressure variation.
Comment 1 Halla Rempt 2016-04-06 15:31:11 UTC
That's probably because Krita doesn't detect the tablet at all and gets mouse events from the system. Since we can not get the hardware, we cannot try to implement support :-(
Comment 2 Bruno Santos 2016-04-07 06:31:11 UTC
Aw man :/ 
Well, I can't give an ETA, but I plan on upgrading to an cintiq, I am from Brazil, but maybe I could ship it to you guys, so you could work on implementing support to others?
Comment 3 Halla Rempt 2016-04-07 06:42:21 UTC
That would be great!
Comment 4 Halla Rempt 2016-06-17 09:25:40 UTC
Can you still reproduce this with Krita 3.0, the builds from https://www.kickstarter.com/projects/krita/krita-2016-lets-make-text-and-vector-art-awesome/posts/1594853 ? If 2.9 didn't crash with a trust tablet, the drivers weren't correctly installed, and with these builds the crash should be gone.
Comment 5 Raghavendra kamath 2018-06-11 04:35:37 UTC
Hi Bruno,

can you please check if this issue still reproducible in the latest version of Krita.

For now I am closing this issue, if you think you can still reproduce this issue in the latest version of krita, please feel free to re-open this issue with relevant information.

Thank you