Link to the plugin page: https://zeroqode.com/plugin/1528983760690x621392331142594600
Demo to preview the plugin:
Introduction
Now you can control your app using only the keyboard. This plugin allows you to set keyboard shortcuts for specific actions in your app, and even override default browser shortcuts.
Set your own keyboard shortcuts, including overriding default browser shortcuts, to open/close menus, popups, submit forms, and more. There are no limits.
How to setup
- Add the JWerty Keys Element
- In the Design Editor, add the JWerty Keys element to your page.
- Capture Keystrokes and Execute Actions
- In the Workflow Editor, add a new action and select Bind Keys A JWerty Keys.
- Define the keys you want to capture (e.g.,
"Enter"or"Shift+A"). - Check the option to trigger an event when the key is pressed
- In the Workflow Editor, add a new event: A JWerty Keys Triggered Keys Used.
- Configure the conditions so that the event is triggered only when the assigned key is pressed.
- Add the actions you want to execute when the key is detected (e.g., save data, open a pop-up, etc.).
Step 1: Bind a Key to an Action
Step 2: Create an Event to Detect the Key Pressed
- Simulate a Key Press
- In the Workflow Editor, add the action Send Keystroke A JWerty Keys.
- Choose the key you want to simulate (e.g.,
"A","Enter"). - Set the event type (keydown, keyup, or keypress).
If you want to simulate a key press without the user physically pressing it:
- Remove Keyboard Shortcuts
- In the Workflow Editor, add the action Unbind Keys A JWerty Keys.
- Specify the key or set of keys you want to remove from the configuration.
If you need to remove a previously configured keyboard shortcut:
Plugin Element Properties
jWerty Keys
Fields:
Title | Description | Type |
–TIP– Register your keys strokes using the element id html to cover the entire app! | ||
First create an element action to bind elements and keys, To bind to an element use #, eg #myID. To bind to a class use a period, eg. .MyClass To more than one you can do this, #MyID1, #MyElement2, .MyClass1 | ||
Once you have finished you can then grab the events such as “Triggered Keys Used” and create only when “keys are ctrl+shift+z” then create some actions. | ||
Separate ID’s with + for all held, , for sequences, regex like so, ctrl+[a-c] or optional like this, ⌃+⇧+P/⌘+⇧+P |
Element Actions
- Unbind keys - TODO: Write description
Title | Description | Type |
To unbind to an element use #, eg #myID. To bind to a class use a period, eg. .MyClass To more than one you can do this, #MyID1, #MyElement2, .MyClass1. To bind complete page keep field “Unbind Element #ID” empy | ||
Seperate ID’s with + for all held, , for sequences, regex like so, ctrl+[a-c] or optional like this, ⌃+⇧+P/⌘+⇧+P | ||
Unbind Element #ID | Element ID to Bind | Text |
Keys To Unbind | TODO: Fill in description | Text |
Unbind all keys | UnbindAll | Checkbox (yes/no) |
- Bind Keys - Bind Keys
Title | Description | Type |
To bind to an element use #, eg #myID. To bind to a class use a period, eg. .MyClass To more than one you can do this, #MyID1, #MyElement2, .MyClass1. To bind complete page keep field “Bind Element #ID” empy | ||
Seperate ID’s with + for all held, , for sequences, regex like so, ctrl+[a-c] or optional like this, ⌃+⇧+P/⌘+⇧+P | ||
Bind Element #ID | Element ID to Bind | Text |
Keys To Bind | Element to Bind | Text |
Prevent Default Action? | Prevent Default Action? | Checkbox (yes/no) |
- Send Keystroke - Send Keystroke
Title | Description | Type |
Fire Element #ID | Fire Element #ID | Text |
Keys To Send | Keys To Send | Text |
Exposed states
Title | Description | Type |
Triggered Keys | Triggered Keys | Text |
Triggered Element Value | TODO: Fill in description | Text |
Element Events
Title | Description |
Triggered Keys Used | Triggered Keys Used |
