Typing behavior, v 14

[kareltucek]

This is Agent side of UltimateHackingKeyboard/firmware#1483

---

New secondary roles page:

• Resolution strategy: <unchanged>

• <new> Minimum hold time:

  • time slider, same as Timeout

  • tooltip:

    The minimum time that a dual role key must be held before it is allowed to trigger as secondary role.

• Timeout: <unchanged>

• <new> Timeout type:

  • radio selection from Active, Passive.

  • tooltip:

    Assume timeout leads to Primary or None:

    Active: timeout action is applied immediately when timeout is reached. Secondary role can no longer be activated after timeout was reached.

    Passive: timeout action is delayed until release. Secondary role can still be triggered until key release.

• Timeout action: <new value>

  • add 'None' option.

• Trigger by release: <removed>

• <new> Triggering event:

  • radio selection from Press, Release, None

  • tooltip:

    • Press: just as with simple strategy, secondary role activated immediately when another key is pressed.
    • Release: secondary role is activated when another key is released while the dual role-key is pressed. Thus the role is determined by the release order of the two keys.
    • None: secondary role key is triggered only by timeout.

• <new> Trigger by mouse:

  • checkbox

  • tooltip:

    When checked, secondary role (usually a modifier in this context) is immediately activated by any mouse movement.

• Trigger safety margin: <unchanged>

• Doubletap to primary: <unchanged>

• Doubletap timeout: <removed?>

• <new> Accept triggers from same half: checkbox

  • tooltip:

    When checked, same half keys don't trigger currently pressed secondary role keys.

[mondalaci]

@kareltucek @mhantsch Would you test it, guys? For me, the secondary roles section feels overwhelming, and there should be a better way to structure it. Any ideas?

[kareltucek]

For me, the secondary roles section feels overwhelming

I totally agree.

and there should be a better way to structure it.

We can add subsections:

• Timeout trigger
  • Timeout* from above
• Keypress trigger
  • Minimum hold time
  • Trigger* from above
  • Accept triggers from same half
• Doubletap trigger
  • Doubletap* from above

I also think that adding presets may be a good idea - maybe a row of preset buttons on the right of 'Secodnary roles' reading things like 'Apply HRM preset', 'Apply time-based preset'...

[mondalaci]

Would you elaborate on preset settings?

@mhantsch What do you think?

[kareltucek]

Would you elaborate on preset settings?

Having (a) button(s) that would set all the values to some sensible configuration that is intended for some specific usecase.

[firngrod]

Summoned by Karel, just dropping in to acknowledge the summon. I'm working, will take a look tonight.

[firngrod]

Doubletap timeout is now global, so that should be removed from secondary roles.
Doubletap to Primary should go under timeout config since it's now something that happens on timeout.
I agree that presets would be good to give the user some reasonable defaults to go off of.

[ert78gb]

Please let me know what will the final agreement and summarise it into 1 comment. thanks

[mhantsch]

@mhantsch What do you think?

This definitely needs some rework. It is currently structured from a technical perspective, not from a perspective of use cases / intended behaviours.

I am currently quite busy but I will add my thoughts how to restructure in a few days.

[mhantsch]

One thing I would definitely change is combining Timeout type and Timeout action into something more compact. These options together describe how the key will behave. I would just use Timeout action to select the combined behaviour.

Timeout action: Immediate primary, Immediate secondary, Immediate none, Suspended primary, Suspended none

Description / Tooltip: Immediate options resolve immediately when the timeout occurs. Suspended options suspend the resolution until key release, and another simultaneous key press will activate secondary resolution instead.

Instead of "suspended", the words "delayed" or "interruptable" are also options.

I am not even offering "Suspended secondary" because I can't see any use case for that.

The second thing that may be worth looking at is creating sections that contain the options that affect this key (the one that has the dual role), and another section that contains the options that are for the trigger key or mouse movement (the options that influence the trigger).

Here's a draft including some re-wording:

• Resolution strategy: ( ) simple / (x) advanced
  • Options for this key
    • Minimum hold time
    • Timeout
    • Timeout action (radio buttons or drop-down, combined with Timeout type as described above)
    • Double tap primary: (x)
    • Double tap timeout
  • Options for trigger
    • Trigger by other key: press / release / none
    • Trigger by mouse: (x)
    • Trigger safety margin
    • Accept trigger key on same keyboard half: (x)

If you do radio buttons for the Timeout action, you could try to arrange them in a visual table-like pattern, or just use a drop-down.

( ) Immediate primary	( ) Suspended primary
(x) Immediate secondary
( ) Immediate none	( ) Suspended none

Some "usual recommended settings" make sense, but I am not yet sure which ones we would need. What are common use cases? Should everything just default to my (?) average HRM settings, and that would also solve all "average user" use cases? If we can agree on some settings, I would put a few buttons to prefill the options directly under the "Resolution strategy" option:

• Resolution strategy: ( ) simple / (x) advanced
  • Recommended defaults: [HRM default] [HRM slow] [Timeout only] <-- clicking these would just set the options below
  • Options for this key'
    • ...

[mondalaci]

@kareltucek What do you think about Max's proposal?

[kareltucek]

Timeout action: Immediate primary, Immediate secondary, Immediate none, Suspended primary, Suspended none

I don't think that merging them completely is a good idea. As a user, I would then tend to think that they are completely different implementations, and so I would be confused and overwhelmed.

I think it would be better to have something like two dropdowns in a single line that would read domething like:

• Timeout action: [primary] activated [immediately].

Sections ...

It makes sense to me and I definitely don't oppose it.

I am not sure whether key-centric (Max's) or trigger-centric (mine) is better though, and I am clearly biased -> someone else should judge this.

Recommended defaults: [HRM default] [HRM slow] [Timeout only] <-- clicking these would just set the options below

Yes, sounds good.

I would just dump there your recommended settings (@mhantsch @firngrod ).

[mhantsch]

two dropdowns in a single line

That would work. It definitely keeps the two things together that define the behaviour, so I like it.
Maybe with a description added to the side that explains the results of the combination.

key-centric (Max's) or trigger-centric (mine)

I realise that timeout is also a trigger, but trigger-centric makes most options fit under the trigger category. I chose key-centric because it creates two sections that are more balanced.

[mondalaci]

I'm quite clueless about these features, and don't use home row mods, but purely from a structural standpoint, I prefer Max's proposal because it's more balanced (5+4 options vs 3+3+2)

Would any of you create mockups for both? They would make it easier to decide which is better.

The "Options for this key" and "Options for trigger" section headers don't read nicely. Maybe "Key options" and "Trigger options" would work, but they may not convey the purpose of these options as well.