- June 17, 2021 at 9:25 pm #27551
Is it possible to resolve the shortcut-key conflict between Snippets and the core, like what’s been done in WordComplete?June 18, 2021 at 1:16 pm #27555
Are you referring to the Snippets plug-in (global) Properties – Keyboard page, or each snippet item properties shortcut?
The global Properties – Keyboard page should be exactly the same as the Word Complete plug-in Keyboard page.
I am not sure what you mean by “resolve”. It doesn’t resolve, but it just shows a warning when there is a conflict.June 28, 2021 at 12:41 am #27577
Sorry for the delay…
I confused the things in the above post.
I mean “each snippet item properties shortcut”.
Currently, a shortcut key assigned to a core command can be assigned to a snippet item without warning.
And there are other issues. Try these steps:
Assign a shortcut key to a core command.
Assign the same key to 2 (or more) snippet items.
Press the key. It shows the snippet items in a menu.
Press Esc key to cancel the menu.
** Issue 1: There’s a sound.
(There’s no sound if the key is not assigned to a core command.)
Now go on:
Suppose the key mentioned above is Ctrl+;.
Assign Alt+; to another core command (X).
Press Ctrl+; to show the snippet items in a menu.
Press Alt key to cancel the menu.
** Issue 2: The core command (X) is triggered (by Alt+;).July 7, 2021 at 1:22 pm #27582
The snippets plug-in item properties should warn you if the keyboard shortcut conflicts with a core command. I am not sure why you didn’t see the warning.
I’ve fixed your second issue.July 9, 2021 at 7:10 am #27587
Um… I can’t recall how I added those shortcuts for the snippet items…
Now I see: It warns only when I changed the shortcut and confirm the dialog.
However, issue 3:
The warning can be bypassed:
Open the Properties of a snippet.
Add a shortcut that conflicts (e.g. Ctrl+N).
Then enable “Use Default Shortcut”.
Confirm and reopen the dialog.
Disable “Use Default Shortcut”.
Confirm the dialog.
** It doesn’t warn.
However again, issue 4:
** Clicking “Edit” button in the dialog always triggers the warning if the shortcut conflicts.
I don’t think it’s necessary.July 9, 2021 at 7:14 am #27589
This thread reminds me of some other suggestions:
The 6th (and other ones).July 9, 2021 at 10:04 am #27591
I’ve fixed these issue and suggestions on 20.8.906.
- You must be logged in to reply to this topic.