Allow rebinding arrow movement keys

[esv]

I'd like to add more convenient keybinds to move up/down/left/right, but couldn't find any commands that do so and binding ArrowUp also showed no conflict despite the fact that arrow keys are bound

[Dimitar - PDF-XChange]

Hello esv,

ArrowUp also showed no conflict despite the fact that arrow keys are bound

May I ask which feature(s), the keys are conflicting with?

Please show me what you see when you try to set these up?

[esv]

May I ask which feature(s), the keys are conflicting with?

they are NOT conflicting, which means that these commands do not exist in the list of commands because if they did, they would show as conflicts. And since they don't exist, I can't assign a different keybinding to them, only default arrow keys work.

[Dimitar - PDF-XChange]

Thanks for the clarification.

I don't think that these were meant to be assigned that way, but just to be sure, I will ask our developers about it.

Will let you know when they respond.

[esv]

Yeah, that's the problem similar to W/B presentation modes - nothing should be exceptional and hardcoded, instead everything should follow the same common architecture so that users can avoid these bumps in the interface

[Dimitar - PDF-XChange]

Hello esv,

May I ask what exactly you are assigning to which feature, as I did try to assign several keys and key combinations, and it worked?

[esv]

I'd like to have more convenient home row keys JKL; as ▼▲◀▶
And also convenient below-home-row keys M, as PgDown/Up

Did you manage to somehow assign them?

Also key combinations don't always work as you've confirmed yourself viewtopic.php?p=197054#p197054

Otherwise not sure what you'd like to know, there are too many keybinds to list them all, and I haven't tested all of them either . I'm just saying that, in general, if nothing is hardcoded, then nothing can block current and future rebinding

[Daniel - PDF-XChange]

Hello, esv

This kind of a change is much easier said than done, which is why progress on this have been gradual, not all at once. Some actions will be seeing changes like this, but at this time some hardcoded actions are intended to be immutable, and I believe the arrow keys fall into that category, due to their varied use in numerous contexts.

For now, you will need to choose different hotkeys when this issue arises, as any changes to which actions are configurable are a long term feature improvement process. It is not a bug and not something we can offer swift changes around.

This topic has already been brought to the Dev team, and if they plan to revise it, we will try to let you know.

Kind regards,