Page 1 of 1

0.84: Rotation hotkeys conflict

Posted: Sun Jan 22, 2017 5:07 pm
by DenTNT
I have set the hotkey combination Ctrl+Right or Ctrl+Left for Image rotation. But XnView MP uses Left and Right keys for Prev/Next files for browsing, so if I set the combination, it will not rotate an image.
Is there a way to disable these global hotkeys?

Re: 0.84: Rotation hotkeys conflict

Posted: Sun Jan 22, 2017 8:04 pm
by cday
DenTNT wrote:I have set the hotkey combination Ctrl+Right or Ctrl+Left for Image rotation. But XnView MP uses Left and Right keys for Prev/Next files for browsing, so if I set the combination, it will not rotate an image.
Is there a way to disable these global hotkeys?
Options > Settings... provides some options to change the default actions, I think from memory, could you have a look and see if you can change the Prev/Next file action and whether that provides a solution?

Re: 0.84: Rotation hotkeys conflict

Posted: Sat Feb 04, 2017 9:58 am
by DenTNT
No.
Settings -> Interface -> Keyboard -> Left/Right
There are only 3 possibilities:
1. Automatic
2. Previous/next file
3. Scroll left/right

Re: 0.84: Rotation hotkeys conflict

Posted: Wed Feb 08, 2017 8:03 am
by xnview
DenTNT wrote:I have set the hotkey combination Ctrl+Right or Ctrl+Left for Image rotation. But XnView MP uses Left and Right keys for Prev/Next files for browsing, so if I set the combination, it will not rotate an image.
Is there a way to disable these global hotkeys?
It works for me, did you change the shortcut for View mode?

Re: 0.84: Rotation hotkeys conflict

Posted: Wed Feb 08, 2017 9:04 am
by DenTNT
xnview wrote:It works for me, did you change the shortcut for View mode?
Sorry, now it works well. Strange...

How can I close the topic?

Re: 0.84: Rotation hotkeys conflict

Posted: Wed Feb 08, 2017 9:18 am
by helmut
DenTNT wrote:
xnview wrote:It works for me, did you change the shortcut for View mode?
Sorry, now it works well. Strange...

How can I close the topic?
:arrow: Closed

Note: I suspect that again the tree with both browser and view mode caused the problem. This confusing tree should be changed, see other topic.