https://bugs.kde.org/show_bug.cgi?id=368849

            Bug ID: 368849
           Summary: [Windows] Krita does not react to Wacom Penabled
                    tabletPC stylus's Top Barrel Button/2nd Switch mouse
                    event on canvas
           Product: krita
           Version: 3.0.1
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: tablet support
          Assignee: krita-bugs-n...@kde.org
          Reporter: tyson...@mail.com

When using a Wacom Penabled TabletPC (Thinkpad X201T, X230T, Cube i7 Stylus)
with a 2 button/switch stylus (UP-911E-02DD) under Windows 10, Krita does not
react to the Top Barrel Button's mouse event on canvas.

Reproducible: Always

Steps to Reproduce:
1. Windows 10 X64 (not tested on other versions of Windows)
2. Krita 3.0.1
3. Wacom Penabled Tablet PC (like: Thinkpad X201T, X230T, Cube i7 Stylus)
4. Wacom Penabled compatible 2 barrel switch stylus (like: UP-911E-02DD)
5. Wacom Feel Driver installed, checked "Use 2 button Pen" and "Hover Click",
Unchecked "Show ripple effect", set Top Barrel Button to Right Click, Bottom to
Middle Click. (same as Ubuntu)

Actual Results:  
Top Barrel Button (mapped as Right Click at the moment) cannot call up Krita's
Popup Palette on canvas. In fact, no matter what mouse event you assigned to
the Top Barrel Button, Krita does not react to them on the canvas. However, In
Settings>Canvas Input Settings, Krita can read the signals sent by the Top
Barrel Button.

Meanwhile, Top Barrel Button Right click seems to be recognized by other apps
on the same Windows 10 system.

Expected Results:  
Krita react to the Top Barrel Button mouse event on its canvas.

Workaround:
1. In Krita's Settings>Canvas Input Settings, change your target action into
"Key combination". In this case, add a Key combination shortcut "Ctrl+P" to
"Show Popup Palette".
2. In Wacom Feel Driver, map Ctrl+P to Top Barrel Button.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to