diff options
author | Nicholas Rishel <rishel.nick@gmail.com> | 2020-05-26 07:02:43 +0300 |
---|---|---|
committer | Nicholas Rishel <rishel.nick@gmail.com> | 2020-10-31 02:29:03 +0300 |
commit | 1f25235ec305e8f448a5d854d3c1bc7500110adf (patch) | |
tree | 1f232f21b6e80215d76aec32485e7043368d1fb1 | |
parent | efe3e4f0233d86a31ef1773de96112a8e628dfb8 (diff) |
Clarify comment to be more specific so that in the future someone knows
the issue with Wintab button events are more significant than simply
setting what buttons should receive button up/down events during context
initialization.
Signed-off-by: Nicholas Rishel <rishel.nick@gmail.com>
-rw-r--r-- | intern/ghost/intern/GHOST_WindowWin32.cpp | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/intern/ghost/intern/GHOST_WindowWin32.cpp b/intern/ghost/intern/GHOST_WindowWin32.cpp index f09be8ed6d0..809faa81177 100644 --- a/intern/ghost/intern/GHOST_WindowWin32.cpp +++ b/intern/ghost/intern/GHOST_WindowWin32.cpp @@ -1363,7 +1363,8 @@ GHOST_TSuccess GHOST_WindowWin32::getWintabInfo(std::vector<GHOST_WintabInfoWin3 outWintabInfo[i].y = pkt.pkY; // Some Wintab libraries don't handle relative button input correctly, so we track button - // presses manually. + // presses manually. Examples include Wacom's Bamboo modifying button events in the queue when + // peeked, or missing events when entering the window when the context is not on top. DWORD buttonsChanged = m_wintab.sysButtonsPressed ^ pkt.pkButtons; // Find the index for the changed button from the button map. |