https://bugs.kde.org/show_bug.cgi?id=406520
Dmitry Kazakov <dimul...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |https://commits.kde.org/kri
| |ta/31c48ac7bf2a4831ade764fc
| |7eba4776e0e56f7b
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Dmitry Kazakov <dimul...@gmail.com> ---
Git commit 31c48ac7bf2a4831ade764fc7eba4776e0e56f7b by Dmitry Kazakov.
Committed on 15/04/2019 at 11:00.
Pushed by dkazakov into branch 'master'.
Fetch tablet mapping from Wintab instead virtual screen geometry
Some devices, like Microsoft Surface Pro 5, don't map tablet's
input range to the entire virtual screen area, but map it to
the primary display that has actual built-in tablet sensor.
In such cases we should fetch actualy mapped aread from Wintab's
lcSys{Org,Ext}{X,Y} fields and use it for cursor mapping.
The patch also introduces an environment variable switch that
falls back to the old method of mapping:
QT_IGNORE_WINTAB_MAPPING=1
When the variable is set, the scaling is done via virtual desktop
area only.
A +171 -0
3rdparty/ext_qt/0027-Fetch-tablet-mapping-from-Wintab-instead-virtual-scr.patch
M +1 -0 3rdparty/ext_qt/CMakeLists.txt
https://commits.kde.org/krita/31c48ac7bf2a4831ade764fc7eba4776e0e56f7b
--
You are receiving this mail because:
You are watching all bug changes.
