The first version of the shortcut system in Flux has grown out of necessity, but lacks a unifying vision. Brooks has taken some time to consider the system and designed a more cohesive approach.
The work required to implement v2:
Verify that all actions that have shortcuts in Flux are covered in the
. Sometimes I’ve found actions that have shortcuts aren’t documented in the Keyboard Shortcut popup. Also, human error might be responsible for missing items.
Swap v1 shortcuts for v2 shortcuts.
Reorganize the Keyboard Shortcut popup to reflect the groupings in v2.
Verify that the shortcuts display correctly in the Context Menu, tooltips, and the Keyboard Shortcut popup, especially across platforms.
There may not be a programmatic system in place to populate tooltips with appropriate shortcuts, and if not, we may not want to build one as part of this effort. But we’ll still need to update tooltips with hardcoded shortcuts to reflect the v2 mappings.
Test that the shortcuts work across browsers and platforms.
Make adjustments where necessary.
Browsers or platforms may cause collisions that weren’t accounted for.
Ergonomic issues might present themselves.
Bonus round: implement infrastructure to handle sequenced, single letter hotkeys. VSCode has these and calls them “chords”. They would give people even more power, like giving focus to a particular layer in PCB simply by typing L and then 4 .
Bonus round #2: show internal-only hotkeys in the Keyboard Shortcuts popup to Flux employees using the new Launchdarkly group.
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
Implementing Shortcuts v2