Macro Jump to Key

General
1

Would it be possible to extend Agent’s “Jump to macro” functionality with a “Jump to Key” list in the main macro pane?

When choosing a macro from Agent’s left panel, it would be nice to populate a list of links to keys assigned to that macro. Something similar to the “Back to Keymap” link that appears when navigating to a macro via the Keymap’s “Jump to macro” button.

Let’s say for some really dumb reason, I have six instances of powerMode toggle lock:clown_face:. I really don’t want to hunt each one down to clean up my config. :sloth: Having “Jump to key” links would make navigation and cleanup sooo much easier.

Jump to Key
Jump to Key1932×586 63.9 KB

Of course, the labeling for the “Jump to” links could be better than what I used in that mockup, but you get the idea…

2 Likes
2

Yes, very much appreciate this functionality. I sometimes can’t remember where I mapped a macro to. Agent shows me it’s on 5 keys, but I have to hunt through all my keymaps and layers to find them. Awkward!

3

Thanks, this seems useful! The positioning of the suggested text seems optimal, but I’d change it to:

This macro is present on QWERTY for PC, base layer, Doom, fn layer, …

When clicking on one such link, Agent would open the relevant layer of the keymap and blink the key several times. Or should it rather open the key action popover to edit the action?

1 Like
4

I would guess opening the popover will cause much less headache to Robi…

5

Let’s make it more concise :slight_smile:

It is obvious that the right side of the screen refers to this macro as it is already showing this macro. So we don’t need to say “This macro is present on…”, but just “Used in:”.
I like the suggestion to indicate keymap and layer.

So we get:

Used in:

  • QWERTY for PC → fn → A
  • QWERTY for PC → mod → B

When clicking on the A or B, the action selection for that key should open. (I think you called it the pop-over.)

We can discuss if clicking anywhere on that line should open the action selection for that key, or if each part should link to the corresponding thing, i.e. clicking on QWERTY for PC should just open the base layer of that keymap, and clicking on fn or mod should just open that layer, but not the action selection.

2 Likes
6

I like your suggestions, although I’m unsure about referencing keys because it depends on the layout, which may not be relevant to the user, even though QWERTY is the standard.

I’d make the whole link clickable as one entity, but I’m unsure whether it should blink the key or open the popover.

1 Like
7

Wow, I finally had an idea that wasn’t idiotic! :partying_face: Laziness really is the best motivator. :laughing:

If you’ve chosen to navigate to the key, then you’re likely planning on disabling it, or making changes to that key action, so linking directly to the key action popover is probably the best move. And from there, you’d only need a click or two to go back out to the desired layer, so I don’t think the separate links is necessary.

8

This may be a bit of a stretch, but what about giving all the keys static hardware IDs, similar to the SWxx numbers printed on the PCB? That could also be useful for clearly communicating specific key issues to the devs in some situations, especially for those using non-QWERTY layouts.

You could display a numeric switchId in the Keymap view, or at least in the key action popover. There’s probably enough room in the upper corner of each key label, or maybe a tooltip on hover?

9

I’m unsure about referencing keys because it depends on the layout

We already have the macro key abbrevs that use the en us layout, so using those to reference the keys in the macro editor is a no brainer.

1 Like
10

I.e., if we want the feature, then I am confident that the following is the way to go:

2 Likes
11

If the key is referenced using the key abbrev, this is a new terminology for users of Agent. It is not shown anywhere else in Agent, is it?

image
image865×433 65.5 KB

Two thoughts:

  1. Maybe the Keyabbrev should be displayed somewhere on this pop-over?
  2. The pop-over already hints with the little notch and the colour on which key it is configured. IMHO, this is absolutely enough - no blinking required, and the indication will tell the user which key has the macro action.
1 Like
12

Thanks for that. I knew there had to be something static to ID them, I just didn’t know where.

There really should be an easy way to note exact key locations for users (like myself) who don’t know their way around GitHub. The popover seems like a good place for that.

1 Like
13

Looks good, and we should display characters instead of key abbreviations.

14
1 Like