- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Sep 2016 21:44:05 +0000
- To: public-pointer-events@w3.org
> I've never maintained a popular drawing program, so I don't know what the typical relationship is between reported pressure and opacity; however, modulating line width with pressure is a near-ubiquitous pattern in tablet-based drawing apps. In fact, the way you know if you're using an app that supports pressure is to press very lightly and see if the line width shrinks. Thanks Brenton. That sounds like an argument for 0.5 being the default to me. Dave? > As far as Android and iOS, they are primarily touch-driven UIs, so they largely circumvent the problem of "What pressure should we map mouse events to?" I don't think that's really true for Android. "MotionEvent.pressure" on Android is there primarily for styluses (and there are lots of Android devices with a stylus - eg. SPen), and needs some default value for touch when there is no native notion of pressure. Eg. I see '1' reported on my Nexus 6p (via `TouchEvent.force`). In that regard I think we've long had this issue already on Android. -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/147#issuecomment-250309850 using your GitHub account
Received on Wednesday, 28 September 2016 21:44:12 UTC