I've been trying to organize my chords after specific purposes. Main overlay:
1 → +9 Loops and Flow
2 → +2 Smooth and Relax
3 → +2 Shape and Deform
4 → +3 HardSurface operations ⇐ this group is an example that I'll discuss below
a → Screen Space Align
b → +4 Mesh
c → Circle
f → Flatten
h → +1 hced operators
x → Scripts
p → Song Chord Prefs
tab → Quick Favorites
Under "HardSurface operations", I want vendor-specific chords. But instead of having a long flattened list of operators, I'd like to show vendor groups like so:
k → +8 Kushiro
m → +4 MACHIN3
o → +3 TeamC
Currently, without nested groups, I'd have to show all vendors on the main page:
1 → +9 Loops and Flow
2 → +2 Smooth and Relax
3 → +2 Shape and Deform
4 → +3 HardSurface operations
a → Screen Space Align
k → +8 Kushiro ⟸ unclear purpose
m → +4 MACHIN3 ⟸ 〃
b → +4 Mesh
c → Circle
f → Flatten
h → +1 hced operators
o → +3 TeamC ⟸ 〃
x → Scripts
p → Song Chord Prefs
tab → Quick Favorites
This gets messy quickly—especially with many addons. I could create groups by purpose, but then I still can't sort operators per vendor. The only workaround is prefixing chords with vendor names (e.g., "Kushiro: Grid Modeler"), which is clunky.
So, I'd love nested groups. The cleanest implementation: a new operator like chordsong.group_enter that takes one string argument, corresponding to group names. If the operator is used, the keymap count should be reflected in the overlay.
I've been trying to organize my chords after specific purposes. Main overlay:
Under "HardSurface operations", I want vendor-specific chords. But instead of having a long flattened list of operators, I'd like to show vendor groups like so:
k → +8 Kushiro
m → +4 MACHIN3
o → +3 TeamC
Currently, without nested groups, I'd have to show all vendors on the main page:
This gets messy quickly—especially with many addons. I could create groups by purpose, but then I still can't sort operators per vendor. The only workaround is prefixing chords with vendor names (e.g., "Kushiro: Grid Modeler"), which is clunky.
So, I'd love nested groups. The cleanest implementation: a new operator like
chordsong.group_enterthat takes one string argument, corresponding to group names. If the operator is used, the keymap count should be reflected in the overlay.