Make touchpads and touch-screens usable for navigating the 3D view (with patch inside)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- computer-graphics, desktop
Research direction
Start by reviewing the attached double_click_drag_means_pan.patch and the existing 3D-view mouse and touch input handling. Confirm the intended Ctrl-drag and quick double-click-then-drag interactions, then verify that panning works on touchpads and touch screens without disrupting normal mouse rotation or zooming.
Written by the indexing model from the issue text.
Description
Hi all,
The following patch enables the following behavior:
- if the mouse drag happens after a previous click with the left mouse button (i.e. a "double click mouse drag"), it will pan instead of rotating;
- panning will also be done instead of rotation if the CTRL button is held down while dragging with the left mouse button.
This enables panning with the mouse-pad or on a touch screen, which is impossible otherwise on some device/OS combinations without sacrificing other useful functionality. Normal mouse operation should not be affected (much) by this addition.
On a touch-screen panning will happen after quick succession of a touch and a drag. With the mouse-pad the preferred way is to hold CTRL down while dragging, but a double-click (two taps) followed quickly (almost like a triple-tap) by a mouse drag will also trigger panning instead of zooming.
I used the CTRL button instead of SHIFT (some other CAD programs do that), because on Windows pressing SHIFT a few times will trigger Sticky keys, while the CTRL key won't have any such effect.
Patch is included here:
double_click_drag_means_pan.patch
Hope it helps !
Cheers,
Csaba
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 210
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CadQuery/CQ-editor
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Crash on renderOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in CadQuery/CQ-editor
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
KalicoCrew/kalico#1012 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
esphome/esphome.io#7657 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
VNG-Realisatie/gemma-zaken#2658 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
comp/gateway comp/plugins duplicate P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NousResearch/hermes-agent#137019 ·
Maintainers usually reply within 1 day