Repository navigation
[Feature] move camera or cursor #1296
Description
Prerequisites
- I have searched the existing issues for a duplicate request.
- I understand that each report must only contain one request. Other requests must get their own report.
The Problem
Using WASD for moving both cursors and camera coupled with the 2d/3d switches is confusing. I often don't remember what is going to move when I use WASD or I'm annoyed because I want the other one to move and have to find a button with the mouse so that I can use WASD to move it. It also interrupts my workflow to switch to a mouse button when Im doing the other operations with the keyboard.
Feature Description
I propose a new paradigm for moving the cursor vs the camera/view. We should make them both moveable with the keyboard and not require clicking a button or using the mouse.
We could allow the arrow keys to move the selection and keep WASD for the camera. That way both could be moved at the same time.
CAMERA
W: forward
A: left
S: back
D: right
SHIFT: down
SPACE: up
CURSOR
UP/DOWN: z axis
LEFT/RIGHT: X axis
PAGE UP/PAGE DOWN: Y axis
Alternatives
Using Capital letters to move the camera and lowercase to move the cursors. In that model the caps lock becomes the toggle instead of buttons. This model has issues since SHIFT is used for moving down and as a modifier. We'd probably have to switch to Right Shift for the modifier. We could map q an z as alternates but this may get confusing.
CAMERA
W: forward
A: left
S: back
D: right
SHIFT: down
SPACE: up
CURSOR
a: z axis
d: z axis
w: x axis
s: x axis
q: y axis up
z: y axis down
Additional context
I think this change would solve a lot of other issues
- Keyboard Focus Lost on Mouse Move #1282
- Problem with the "move selected" button #966
- [Bug Report] Move Selection eventually moves on it's own when you hold it. #882
- Problem with the "move selected" button #966
- [Bug Report] Wayland mouse input problems #976
- Add hotkeys to rotate Camera #773
maybe this one too
Activity
jtmoree-github-com commentedon Feb 28, 2026
I have created a fork and wired up a number of user interface changes. We may not want to merge it but it is useful as a demo of what I'm trying to accomplish. It's at https://github.com/jtmoree-github-com/Amulet-Map-Editor/tree/new_interface
This issue is addressed in that code by 2 changes.
jtmoree-github-com commentedon Mar 1, 2026
I created another branch that i call breaking changes. Feel free to examine as a proof of concept redesign.
gentlegiantJGC commentedon Mar 14, 2026
I am interested in exploring alternative control schemes but I don't know how much this would get used.
jtmoree-github-com commentedon Mar 15, 2026
I have created a prototype rewrite to experiment with different ideas.
I bring this up because I agree this is not a critical issue but I find the current keyboard support limiting and frustrating which is why Im trying different ideas. fyi. i also redesigned the user interface in that branch but that's a different set of issues. just be aware if you do try it out.
https://github.com/jtmoree-github-com/Amulet-Map-Editor/tree/breaking_changes