I’m developing a timeline animation plugin that uses standard editing shortcuts such as Delete, Ctrl+C, Ctrl+V, Ctrl+X, and Ctrl+D. These actions should behave like any native editor: when the plugin’s timeline is the active editing context, these shortcuts should operate on the plugin instead of Studio.
Here is an example of my problem: Ctrl+X cuts selected instance rather than selected keyframes.
PluginActions should be toggleable via context, if I have keyframes selected, pressing Delete should delete those keyframes rather than deleting the currently selected instance(s) in Explorer.
However, this shouldn’t simply be tied to whether the plugin is open or focused. The plugin should be able to decide when it wants to override Studio’s shortcuts. Since plugins would then have the potential to unexpectedly change studio there should be a “Modify Studio Shortcuts” toggle added in the Plugin Management window.
If no keyframes are selected, or if the plugin has no relevant action for the current shortcut, it should allow Studio to process the input normally. When the animation file is closed (or the plugin loses focus), the plugin would disable its actions entirely, allowing Studio’s default shortcuts to resume as normal.
These capabilities would allow plugin developers to create plugins with shortcuts that integrate seamlessly into studio’s existing workflow without forcing their plugin’s users to learn/create an arbitrary set of keybinds.