As a future request, I think it would be very useful if users could control the map using the keyboard.
Suggested keyboard controls:
• W – move up
• A – move left
• S – move down
• D – move right
• O – zoom in
• I – zoom out
• R – reset map view (my current location)
• T – show info bar (top left) with current altitude (Toggle on/off)
📌 When the user zooms in or out, briefly display a small indicator with the current zoom level.
As a future request, I think it would be very useful if users could control the map using the keyboard.
Suggested keyboard controls:
• W – move up
• A – move left
• S – move down
• D – move right
• O – zoom in
• I – zoom out
• R – reset map view (my current location)
• T – show info bar (top left) with current altitude (Toggle on/off)
📌 When the user zooms in or out, briefly display a small indicator with the current zoom level.
<!-- github-sync-id:3883135679 -->
Additionally, I'd suggest to use Z for move down instead of S. I know WASD is common for gaming, but on the T-Deck the Z has a more logical placement on the keyboard.
Additionally, I'd suggest to use Z for move down instead of S. I know WASD is common for gaming, but on the T-Deck the Z has a more logical placement on the keyboard.
<!-- github-comment-id:3834938709 -->
Additionally, I'd suggest to use Z for move down instead of S. I know WASD is common for gaming, but on the T-Deck the Z has a more logical placement on the keyboard.
Interesting idea. I personally rest my fingers on WASD by default, and all the keys are reachable without extra movement. From my perspective, Z requires moving the finger slightly downward. In the end if that is the case with the buttons, "S" could be repurposed to toggle a small status bar in the top-left corner of the map, showing altitude, speed (km/h), and similar info.
Honestly I'm fan of the WASD 🤣
> Additionally, I'd suggest to use Z for move down instead of S. I know WASD is common for gaming, but on the T-Deck the Z has a more logical placement on the keyboard.
Interesting idea. I personally rest my fingers on WASD by default, and all the keys are reachable without extra movement. From my perspective, Z requires moving the finger slightly downward. In the end if that is the case with the buttons, "S" could be repurposed to toggle a small status bar in the top-left corner of the map, showing altitude, speed (km/h), and similar info.
Honestly I'm fan of the WASD 🤣
<!-- github-comment-id:3837206941 -->
I think this works great with the 0.9.8 release, but it seems the "T" setting is not persistent across reboots. See https://github.com/dabeani/meshcore/issues/87.
<!-- github-comment-id:3887551970 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As a future request, I think it would be very useful if users could control the map using the keyboard.
Suggested keyboard controls:
• W – move up
• A – move left
• S – move down
• D – move right
• O – zoom in
• I – zoom out
• R – reset map view (my current location)
• T – show info bar (top left) with current altitude (Toggle on/off)
📌 When the user zooms in or out, briefly display a small indicator with the current zoom level.
I'd like to add "move up/down/left/right with trackball on T-deck" to that :)
Additionally, I'd suggest to use Z for move down instead of S. I know WASD is common for gaming, but on the T-Deck the Z has a more logical placement on the keyboard.
Interesting idea. I personally rest my fingers on WASD by default, and all the keys are reachable without extra movement. From my perspective, Z requires moving the finger slightly downward. In the end if that is the case with the buttons, "S" could be repurposed to toggle a small status bar in the top-left corner of the map, showing altitude, speed (km/h), and similar info.
Honestly I'm fan of the WASD 🤣
Lets go ahead with the first suggestion - and then we will decide how it works!
implemented in v0.9.8!
I think this works great with the 0.9.8 release, but it seems the "T" setting is not persistent across reboots. See https://github.com/dabeani/meshcore/issues/87.
fixed in v0.9.9!