Closed GrewHair closed 2 months ago
Seems reasonable enough :)
Does this work for the use case? https://github.com/jtroo/kanata/pull/1250
Wow that was quick, thanks!
Haven't tested it yet, as I'm using the wintercept version, and apparently it doesn't build now. Filed #1253 for that.
Commented out a bunch of lines in parser/src/cfg/mod.rs
for now, haha :) And yeah, it does work! Will come back after more testing.
Ok it works perfectly for me, thanks @jtroo! Should I close the issue?
Is your feature request related to a problem? Please describe.
My use case is rather complex, so I hope you'll excuse me for not going into gory details right away.
I'd rather just say that while Kanata now provides various handy devices/hacks that allow to store and reuse "state" for complex scenarios, like key-history, noop keys, virtual keys, etc, I feel like sometimes it would just make more sense to piggyback on Kanata's own wonderful layer model, keeping config cleaner and saner. Also just for completeness' sake.
So we already have a predicate that checks the current layer in
switch
statements, thanks to #1060. How hard would it be to also make one for the current base layer (the one Kanata goes back to when you releaselayer-while-held
)?Describe the solution you'd like.
a check for current base layer, like this:
Describe alternatives you've considered.
Defining dummy virtual keys and using them as flags that other bool expressions can query.
Additional context
No response