Thank you for the think tank. I like the good discussion on this topic.
My opinion is as follows:
1. I do not want the confirmation short presses as per my previous sketch anymore. I think that rprosperi is right that too many clicks is looking for trouble.
2. I also want to say, that this is an experimental platform, and I am willing to try different bits.
3. We don't have to decide on one solution only. Options that are not clashing, can co-exist. And a config flag is not a problem either.
I definitely think the f/g option can stay as base level control any way. There is no reason why the f/g cycle on the shift should change with the options discussed.
As a technical point, the way I want to hack it into the system is that whichever shift method will still activate the internal shiftF and shiftG flags, and then execute FN normally as if you pressed shift. That is what the shift cycle hack is doing already. The WP43S system will care for the correct dispatch. That way the dispatch function remains centralised and has common upgrades from Martin in future.
4. I like H2X's proposal:
- Press (display FN1) + release = execute FN1 (the normal, short press function).
- Press (display FN1) + hold (display f(FN1)) + release = execute f(FN).
- Press (display FN1) + hold (display changes to f(FN1)) + hold (display changes to g(FN1)) + release = execute g(FN).
- Press (display FN1) + hold (display changes to f(FN1)) + hold (display changes to g(FN1)) + hold (regardless of release) = NOP
I did a sketch for it this morning but had internet issues to prevent connection and post. It should say the same thing.

- IMG_0989.png (45.25 KiB) Viewed 1878 times
5. I also like Dani's new proposal though. The similarity to the double shift to get g is appealing.
- Pressing the function key [FN] once, normally or briefly triggers the function [FN]
- One extended press of the function key [FN] triggers the function f[FN].
- Pressing the function key [FN] twice triggers the function g[FN].
6. From a programming point of view H2X's is easier I think. I may try that in the week some time.
7. I also actually think Dani's (2) can at first co-exist with H2X (2). I could add a config flag if needed later. And Dani's (3) can also co-exist.
8. I also like the long press shift idea for HOME menu. That can also co-exist with the triple shift.
Jaco