Misleading clock parameter TimerAlwaysFires / eggtimer versus metronome

I got a bit confused of the counter intuitive clock parameter TimerAlwaysFires.
When the application is on screen the clock timer always fires independently if Set Clock.TimerAlwaysFires is set true or false.
Here is an example to implement a "one shot" eggtimer and a "always firing" metronome


clock_eggtimer_metronome.aia (41.2 KB)

I fell for this too.

See What means TimerAlwaysFires?
for my test results correcting my misconception.