Josh Goebel

You could possibly then have self-focusing modals: ```py keymap("Grave"), { C("Alt-Grave"): [UC(0x0060), C("Shift-Left"), go_modal], C("A"): UC(0x00E0), # à Latin Small a with Grave C("E"): UC(0x00E8), # è Latin Small e...

I'm not sure I follow you at all. A nested keymap with `after:miss : [UC(0x0060), cancel_modal, reinject]` is going to behave ALMOST exactly like a top-level keymap in your current...

> So really that would just leave these two(?) lines that still need to be in every nested keymap. I think that sounds right since you're wanting special behavior from...

Could you please define depth buffer or give a code example? All I see here is a visual effect. There may be a depth buffer, but this animation doesn't prove...

I'll vote with @Weeppiko here for whatever it's worth - we should avoid adding "magic" features that don't map back onto the defined memory/virtual hardware. In a perfect world one...

I'm not sure I follow what this is saying: > The depth buffer uses vbank switching vbank(0)/vbank(1) into which you can write/read.

> The buffer is magic (exists somewhere completely hidden from the user); It's not, it's addressable in VRAM as mentioned earlier.

Oh I was quoting nesbox but I think he was talking about OVR... sorry, I'm not even sure I'm following what this whole depth buffer thing is.

> would have unbounded memory This is not desirable. The WASM runtime has limited RAM on purpose. (feel free to go back and find the issues around it's development and...

IMHO we should really consider semantic versioning. In that case most every release would be minimally a minor release. Ie 1.2 1.3 1.4 Etc