prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.72k stars 1.93k forks source link

Object right-click menu very hard to access - always triggers panning with even the slightest movement #3838

Open VanessaE opened 4 years ago

VanessaE commented 4 years ago

Version

git commit 45e00793567782b0103bca0bc2e266be708a32a2

Operating system type + version

Debian sid

3D printer brand / version + firmware version (if known)

Not important (but it's a Hypercube with dual extrude)

Behavior

  1. Load any model.
  2. Right click on it. The view pans and no menu is presented.
  3. Try again. It pans again.
  4. Retrieve the mouse from the other room you threw it into, and try again. :grin:

Prusa Slicer keeps triggering its pan feature if you happen to move the mouse even one pixel while right-clicking.

By comparison, upstream Slic3r doesn't allow panning when right-clicking on an object -- you have to right-click on something other than an object to get it to pan.

Both behaviors are a problem, but right clicking an object causing the view to pan is far more frustrating, because if I intend to summon the right-click menu in Prusa, I have to really CRAM my mouse down onto the desk to make sure it can't move even in the slightest, which is not only cumbersome, but also possibly injurious (to say nothing of what that amount of pressure is doing to the mouse), but in upstream I can zoom out if needed to find some empty space to right-click on.

I suggest making right-click behave as in upstream Slic3r, only popping up a menu, and requiring a modifier such as Shift, Ctrl, or Super to trigger panning the view (don't even think about using Alt, my desktop window manager already uses that, as do many others). Or, invert that behavior, letting a modifier cause the menu to pop-up, panning otherwise.

Project File (.3MF) where problem occurs

N/A

kephail commented 3 years ago

I have this issue too (on Mac) - it was driving me mad. Funnily enough the solution that worked for me which I didn't consider was what @VanessaE suggested (CRAM my mouse down onto the desk 😆 ). Not an ideal solution.