Not Understanding Tap Timeout

[thomastthai]

I am testing the concept of tap timeout. "Tap timeout" is confusing. Perhaps changing the wording to "tap re-press timeout" would make more sense. After reading the extended explanation, 'Tap timeout in more detail', several times, I'm still confused and could use help.

Let's start with what tap timeout means:

The tap timeout is the number of milliseconds within which a rapid press+release+press of a key will result in the tap action being held instead of the hold action activating.

Does that mean just those three sequences: press, release, press or could it be more like: press, release, press, release, press?

Let's simulate with some code:

(defcfg
  process-unmapped-keys yes
)

(defsrc
  a   s  
)

(defvar
  ;; The tap timeout is the number of milliseconds within which a rapid 
  ;; press+release+press of a key will result in the tap action being 
  ;; held instead of the hold action activating.
  tap-repress-timeout 200
  hold-timeout 200
)

(deflayer base
  @a  @s  
)

(defalias
  a (tap-hold $tap-repress-timeout $hold-timeout a lmet)
  s (tap-hold $tap-repress-timeout $hold-timeout s lalt)
)

Attempting to simulate rapid press-release-press of the a key with the Simulator:

My intention is to use 210ms to press-release-press a:

d:a t:70 u:a t:70 d:a t:70 u:a t:100

The output:

t:              70ms
out:   ↓(press) A
t:              6ms
out: ↑(release) A
t:              64ms
out:   ↓(press) A
t:              70ms
out: ↑(release) A

210ms > 200ms, so why does the tap action still take place?

[gerhard-h]

doing d:a t:70 u:a t:70 d:a t:300 u:a t:100 would result in aaaaaaaa... but the amout of a (after the second a ) is handled by your OS and not simulated