Better submaps

[ItsOhen]

Describe your PR, what does it fix/add?

Addresses: #10659
But not quite a good solution yet.
What i really wanted was a syntax like this:

submap = someSub {
  oneshot = true
  bind ,x,exec ...
  submap = Layer2 {
    oneshot = false
    bind ,x,exec ...
   }
}

Then a stack of submaps to keep track of where we are.
Hyprlang doesn't really allow for this though. So this is what i ended up with.
Using the syntax:

bind = $mainMod, a, submap, someSub
submap = someSub oneshot
bind = ,q,submap, reset
bind = ,e,exec,...
bind = ,w,submap,Layer2

submap = Layer2 oneshot
bind = ,q,submap, reset
bind = ,e,exec,...
bind = ,w,submap, Layer3

submap = Layer3 oneshot
bind = ,e,exec,...
bind = ,q,submap, reset
submap = reset

With it being just strings floating around it's really hard to cascade parents.
So for now if a submap is oneshot, it just resets submap to default.
I made a version using containers instead which made it trivial to go to nearest none oneshot, but felt heavy and unnecessary without a different way to nest submaps. Like, how many layers are people really going to put in?

Is it ready for merging, or does it need work?

Probably not. Some suggestions on how to make this look better would be nice.

[vaxerski]

I don't see the point. Why not just use the current submaps to move to and from? It doesn't address the issue to me?

[ItsOhen]

? Wasn't the issue that there should be a way to go back to default submap when a keybind is triggered?
Which is what this does.
If submap is oneshot, go back to default after a dispatcher is called.
If not, stay in w/e submap you are in until a reset or some other submap is called.

And the reason i moved it to a struct was so that hopefully in the future there is a better way to parse { }, and then it would be easy to make a neat push pop stack structure for submaps.
Maybe something like:
while(p->parent && p->oneshot) { m_submap.pop(); p = p->parent; }

[vaxerski]

oh yeah sorry got confused there with your description

[ItsOhen]

Fucking cf.. I don't even know anymore. I auto run it on save. Complains. Manually run it before squash, still complains. Stage, run, commit, still complains. Like come on. Explain this to me:

[vaxerski]

rest lgtm, needs a wiki mr

[vaxerski]

tests needed, code OK