gpxstudio / gpx.studio

The online GPX file editor
https://gpx.studio/
MIT License
125 stars 20 forks source link

3d view navigation arrow keys conflict with list of tracks #44

Open pfbreton-perso opened 1 month ago

pfbreton-perso commented 1 month ago

Repro steps:

1- turn on the vertical list of tracks 2- load multiple GPX files to have a list of ~4 or 5 (or more) items 3- switch to a 3d view 4- use the keyboard arrows to navigate the view (up down left right)

problem: the active 9select) track also changes with the arrow keys

see video: arrow_keys_conflict

i don't know how you can define which windo gets focus. maybe an alternative approach would be to use the WASD keys to bavigate the 3d view?

vcoppe commented 1 month ago

I do not use these map navigation shortcuts so I did not notice this shortcut conflict.

Do you think they are essential? The simplest fix would be to disable them.

Changing them is not really an option since they are native Mapbox GL JS shortcuts. Changing the shortcuts to navigate files would not make much sense either.

I tried to implement something based on the user focus but I find it quite confusing.

pfbreton-perso commented 1 month ago

I think it’s a minor issue that can be ignored given the challenges to fix it

Le lun. 5 août 2024 à 09:42, vcoppe @.***> a écrit :

I do not use these map navigation shortcuts so I did not notice this shortcut conflict.

Do you think they are essential? The simplest fix would be to disable them.

Changing them is not really an option since they are native Mapbox GL JS shortcuts. Changing the shortcuts to navigate files would not make much sense either.

I tried to implement something based on the user focus but I find it quite confusing.

— Reply to this email directly, view it on GitHub https://github.com/gpxstudio/gpx.studio/issues/44#issuecomment-2269486406, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOGDLG2PZ2LXTOQDRNCEW33ZP6TP3AVCNFSM6AAAAABLWO5EXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZGQ4DMNBQGY . You are receiving this because you authored the thread.Message ID: @.***>