Bug: Custom shortcuts not saved on exit after upgrading to 1.10.1 [RESOLVED]

[Pipty]

After upgrading to 1.10.1, XnView MP would not save my customized shortcuts. I have to reassign the keys each time I start the program. This bug didn't appear in previous XnView MP versions on my local machine.

XnView MP Version: 1.10.1
XnView Installation Methods: bug reproduced in both win64 setup and portable version
OS: Windows 11 Pro 10.0.26200 Build 26200
Expected behaviour: program should save my assigned shortcuts even after I close the program.
Actual behaviour: When XnView is relaunched, shortcuts are set back to default.
Note: other customized settings would not be reset upon relaunch, the only broken part is the Shortcuts.

Steps to reproduce:
1. Launch XnView MP.
2. Assign PgDown to cmd_historyNext, PgUp to cmd_historyPrev via Settings>Interface>Shortcuts, and click 'OK'.
3. PgDown and PgUp now can go Forward/Back when exploring the folders in browser.
4. Close XnView MP.
5. Relaunch XnView MP.
6. PgDown and PgUp no longer function as Foward/Back.

I have searched across the forum and found out that this bug appeared multiple times over the past years. I have tried all solutions mentioned in the posts and had no luck.

This bug persists no matter how I change the Settings>Integration>Paths:
1. Current User (Recommanded): this is the default I was using when I first noticed the bug.
2. Portable (Application Folder): bug persisted.

This bug persists no matter how I change the user privileges:
1. I have tried giving full control over the following files, yet the bug persisted:

• Thumb.db

• XnView.db

• default.bar

• default.keys

• xnview.ini

2. I have tried running the program as administrator, the bug persisted.

I have checked the content of the default.keys, the customized shortcuts were actually saved in this file:

Code: Select all

cmd_historyNext PgDown

Code: Select all

cmd_historyPrev PgUp

However, XnView MP refused to load default.keys on relaunch.
I have also tried manually loading the default.keys file via Settings>Interface>Shortcuts>Load..., and nothing changed.

I have tried modifying xnview.ini and changed relative path to absolute path, yet bug persisted:

Code: Select all

shortcut=default.keys

Code: Select all

shortcut=C:/Users/UserName/AppData/Roaming/XnViewMP/default.keys

Since this bug appeared multiple times across different versions/OS in the past and keep recurring, it should worth more importance.

[jkm]

Welcome to the forums, Pipty...

I can tell you did a good amount of exploration here, but just a little bit more and you would have hit on the truth. The situation is not quite what you think.

It's not saving customized shortcuts that doesn't work, it's assigning the PgUP and PgDn keys. If you try and assign those keys to ANY command (not just the two you listed), they're forgotten at app restart in exactly the way you describe.

But if you assign a DIFFERENT key to cmd_historyNext and cmd_historyPrev, it works just fine. For example, I was able to assign Alt-PgDn and Alt-PgUp to these, and it saved and remembered it after restart with no problem.

I wonder if this is a conflict with PgUp/PgDn being needed to "scroll" the Browser window itself...

In any case, I suggest you use another key, or a modifier (like Ctrl/Alt/Shift) as I did above on PgUp/PgDn until Pierre comments if this behavior with PgUp/PgDn is intentional.

Please test a bit more, and you will probably find saving any other shortcuts works fine. Please confirm that's the case.

Cheers...

[xnview]

PgDown and PgUp can't be changed in browser

[Pipty]

Welcome to the forums, Pipty...

I can tell you did a good amount of exploration here, but just a little bit more and you would have hit on the truth. The situation is not quite what you think.

It's not saving customized shortcuts that doesn't work, it's assigning the PgUP and PgDn keys. If you try and assign those keys to ANY command (not just the two you listed), they're forgotten at app restart in exactly the way you describe.

But if you assign a DIFFERENT key to cmd_historyNext and cmd_historyPrev, it works just fine. For example, I was able to assign Alt-PgDn and Alt-PgUp to these, and it saved and remembered it after restart with no problem.

I wonder if this is a conflict with PgUp/PgDn being needed to "scroll" the Browser window itself...

In any case, I suggest you use another key, or a modifier (like Ctrl/Alt/Shift) as I did above on PgUp/PgDn until Pierre comments if this behavior with PgUp/PgDn is intentional.

Please test a bit more, and you will probably find saving any other shortcuts works fine. Please confirm that's the case.

Cheers...

Thanks for the reply, I have tested Alt+Pgdown and Alt+PgUp. The changes successfully saved. Everything works fine now.

Just curious since this wasn't the case with previous version before I upgraded to 1.10.1. In the previous version, I have assigned the exact keys to the exact commands, and they were saved successfully. Even after I restarted the program, the customization persisted.

If PgDown and PgUp aren't supposed to be assigned, then it means what I have been using for more than half a year was not a feature, but a bug instead?

Btw how can I close my post as closed?

[jkm]

You don’t have to mark it as closed, don’t worry about it. You could just edit the subject of your original post to start it with RESOLVED. Pierre, who replied above, is the developer, so since he said those keys can’t be assigned, it’s intentional and he'll just ignore the thread.

I don’t recall ever trying to assign those keys myself, because I use them for scrolling. So perhaps as you say it was an accidental feature.

But in 1.10.1 some low level changes were made in how some configuration was saved and loaded, to support some new features being introduced, and perhaps as a result the loophole no longer works. That’s about all I can say about it.

Anyway I'm glad you’re squared away.

[xnview]

If PgDown and PgUp aren't supposed to be assigned, then it means what I have been using for more than half a year was not a feature, but a bug instead?

Strange, it doesnt work with previous version too