Like we can customize folder settings, it should be possible to use didderent modes depending on the view mode.
For example, i configured "left" & "right" arrows to enter a folder & go back, which is quite nice. But when in miniatures or tiles modes, the navigation is, of course, impaired. I had to change the "up" & "down" arrows to select next/prev. But this also has drawbacks: it isn´t possible to skip through rows of thumbnails to navigate, but rather have to run through all files (pushing the according letter is also possible, yes) & using "previous" on the first item will "loop" backwards to the end of the lst & vice versa (actually this isn´t even bad, if it was an option in the freferences).
So basically this could be an option in the "buttons" dialog to restrict the hotkeys to certain modes. It is very nice to use the keyboard & this would be very helpful in order to avoid key conflicts.
Wouldn't it be better to choose hotkeys that don't conflict so that you can use the same ones in all modes? (At least for actions like back/forward that you could want to use in all modes.)
Normally i use Enter to enter & ctrl-left/right for "go forward/back", but this also conflicted with some stuff (which was ok for me in that case), like selecting files in thumbnail mode. But the left/right navigation is much quicker, so i´d like to keep it like that. Looking into lots of folders is much easier, since it´s onyl the four arrow keys to navigate.
The problem is anyway, if you use over hundred shortcuts, like me, that you either have conflicts or you have more uncomfortable combinations, which is the case when having to use qualifier keys for the most basic navigations, like "right arrow" is better to handle than "ctrl-right arrow". In the details mode, which i use most, there is only vertical movement, so this is ideal. There is a few things, where more granular rules would be handy. I also use the space bar to toggle lister sides, which is very practical, but it is then not available for some selecting toggling, etc.
The idea with those combinations was to mimic the behavior of windows folder tree (although i don´t use the tree anymore) where the four arrow buttons work like that, providing quick navigation with minimal hand movements & without to have to use the qualifier keys.
Well, i set it back, because Ctrl-Left/Right will also do it so far. But the "granular" thing would be still interesting, of course.
But one question, is this button code correct?
GO {f}
Go Forward
The idea is, if there is no "go forward" option (because the path hasn´t be entered yet in that session), GO {f} would be valid. But maybe i am thinking wrong & there is a catch?! Because it seems, that GO {f} is a sufficient replacement for Go FORWARD, making that command obsolete.
