From 7f5ad7b57144144dcaf8646f8315d63025eb83ad Mon Sep 17 00:00:00 2001 From: Jorian Rutten Date: Tue, 19 Aug 2025 03:13:28 +0200 Subject: [PATCH 1/2] Add 'Command' explanation to `.aseprite-keys` documentation Added a paragraph to explain that you need to create custom commands to be able to hook up custom key shortcuts to extension functionality. Added link to API documentation for :NewCommand() --- extensions/keys.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/extensions/keys.md b/extensions/keys.md index 9c67a96..d26b742 100644 --- a/extensions/keys.md +++ b/extensions/keys.md @@ -46,6 +46,12 @@ can be created / exported from [Edit > Keyboard Shortcuts](keyboard-shortcuts.md ``` +When creating a keyboard shortcut for custom functionality in an +aseprite extension, you must create a New Command for it first. +You can then use that Command's Name to bind the functionality to +the shortcut using the `.aseprite-keys` file. + +You can read more on how to create Commands in the [API documentation](https://www.aseprite.org/api/plugin#pluginnewcommand) --- From b8a170ff9e65e8f800f59260d78e0320164b09cc Mon Sep 17 00:00:00 2001 From: Jorian Rutten Date: Tue, 19 Aug 2025 03:28:47 +0200 Subject: [PATCH 2/2] Changed 'name' to 'title' to match Command properties --- extensions/keys.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/extensions/keys.md b/extensions/keys.md index d26b742..0221abb 100644 --- a/extensions/keys.md +++ b/extensions/keys.md @@ -48,8 +48,8 @@ can be created / exported from [Edit > Keyboard Shortcuts](keyboard-shortcuts.md ``` When creating a keyboard shortcut for custom functionality in an aseprite extension, you must create a New Command for it first. -You can then use that Command's Name to bind the functionality to -the shortcut using the `.aseprite-keys` file. +You can then use that Command's title to bind the functionality +to the shortcut using the `.aseprite-keys` file. You can read more on how to create Commands in the [API documentation](https://www.aseprite.org/api/plugin#pluginnewcommand)