Toggle editor layout shortcut not working after update

Operating system

Windows

Joplin version

3.0.12

Desktop version info

Joplin 3.0.12 (prod, win32)

Client ID: 6cd667061e4a450dadcb5e41273a4348
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: a64d6e3

Code-Clipboard: 1.0.0
Convert Text To New Note: 1.5.1
Embed Search: 2.0.0
Enhancement: 1.2.1
Inline tags: 1.2.1
Joplin DDDot: 0.2.0
Journal: 1.1.2
Math Mode: 0.6.2
Note list (Preview): 0.4.0
Note Rename: 1.0.0
Note Tabs: 1.4.0
Quick HTML tags: 0.2.0
Quick Links: 1.2.4
Quick Move: 1.1.0
Search & Replace: 2.2.0
Simple Backup: 1.3.6
Templates: 2.4.0

Editor

Markdown Editor

What issue do you have?

I changed the default keybord shortcut from Ctrl + L to Ctrl + Space. After installing the update to version 3.. my shortcut changes were gone, so I imported them with the help of the backup plugin. However, Ctrl + Space isn't working as the shortcut to toggle the editor layout anymore. Even if I have that as the shortcut, only Ctrl + L toggles the layout reliably. Ctrl + Space only works if I'm in the editing view and the cursor is active.
Additionally, the shortcut under view still lists Ctrl + L as the shortcut for toggling the editor layout, even after I've changed it to Ctrl + Space.
Is anyone else having this problem?

The following issue seems related as toggling with Ctrl+Space only works with the editor focused:

Ctrl+Space persists as the shortcut on my end.

That's interesting, but it seems like it isn't a new issue. Ctrl + Space worked fine for me before the update

Okay, nevermind, it's working fine again, I don't know why it didn't before. Maybe I didn't do a proper restart after changing the shortcuts and just closed the app, I don't remember. But probably user error.

This isn't user error. I don't expect needing to restart to make a keyboard shortcut take effect. If expected, the Keyboard Shortcuts page should explain it in plain language.

Even if it were expected, two keyboard shortcuts triggering the same command at any point seems like a bug.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.