Skip to main content
Question

Bug can not move board with spacebar or right click when using wacom pen

  • February 3, 2026
  • 1 reply
  • 6 views

Forum|alt.badge.img

When using a wacom graphics tablet with the draw tool it is not possible to move the board/View with space or rightclick, instead the draw tool creates a line 

 

expected behaviour: when the hand to move shows from pressing space the pen moves the view/board

current behaviour: a line is drawn instead of the view being moved 

condition: this is only happening with the graphics tablet not with mouse

Comments

alison cheney
Forum|alt.badge.img+4
  • Lucid community team
  • February 3, 2026

Hi ​@per,

Thank you for posting in the Lucid Community!

I understand how this would disrupt your workflow. To take a closer look at the issue you’re experiencing, could you try the following workarounds?

  • The most common cause is Windows Ink. While it’s meant to help with handwriting, it often forces the browser to treat every pen touch as a primary click/draw action, ignoring keyboard modifiers like the Spacebar.
  • If you are using a Chromium-based browser (Chrome, Edge, or Brave), the browser engine itself might be the bottleneck. These browsers are notoriously aggressive with pen input. Firefox uses a different engine (Gecko) to handle “Pointer Events.” Many users find that Firefox respects the Spacebar + Pen combo perfectly while Chrome fails.
  • In your browser settings, search for “Hardware Acceleration” and toggle it to the opposite of its current setting. This changes how the browser communicates with your graphics card.
  • It’s possible that WebGL is causing an issue with your graphics card.

  • If the pen gets stuck in “draw mode,” try pressing “P” (Freehand Draw) and then “V” (Selection Tool). This manual toggle can force Lucid to re-sync the active tool with your pen's input.
  • Some users report that switching the Selection Mode (in the primary toolbar) from “Box” to “Freehand” clears the conflict.

Please let me know if you are still running into issues after attempting the workarounds above. Thank you for your help and patience!