Better support for toggles in FN layers

[slow raft]

Currently when making a toggle in an FN layer through the advanced keys section, you need have the FN layer active to toggle it on, but you don't to toggle it off. This makes toggles pretty much unusable with FN layers, since if I wanted to bind a toggle to my E key or something, it would toggle off the second I start typing on the main layer. There should be an option to only untoggle FN layer toggles when the respective FN layer is active. Along with that, the active state RGB for the toggle (white light when toggle is on) should only be visible in the FN layer.

Additionally, I have a couple of QoL suggestions to make toggles more customizable.

1. It would be nice if we could change the color of the active state RGB for toggles like we can with caps lock.
2. It would also be nice if we could make toggles show up on the light indicator for the 80HE. Currently there's only an AnyKeyActuated condition in the effect creator, but a SpecificKeyActuated condition or even just a condition exclusively for toggles would be great.

[noble pumice]

You know advanced keys hold feature exist right

Also you can already change capslock on rgb in wootility

[slow raft]

It seems like you've misinterpreted pretty much everything in my post. Please reread it more carefully

[slow raft]

Again, please reread the post. I specifically addressed the fact that you can do this with caps lock and said I wish you could do it with custom toggle keys as well.

[noble pumice]

Ooh

XD

@slow raft ask it in wootility updates

You would get answer faster over there

[slow raft]

Oh I didn't notice the feedback thread there lol, thanks!

[proud mural]

Yeah, this is just a bug. The QoL suggestions would be nice to have, I hope they get implemented.

[slow raft]

Is the bug on their radar? Like have they said anything about fixing it?

[proud mural]

They don’t really have a public bug tracker that they go by, so I’m not sure. I haven’t seen this exact bug reported before though, so I doubt it. I did find this: https://github.com/WootingKb/wootility-issues/issues/304, it’s not the same but you can see the same behavior in his linked video.

I think only fairly easy bugs get solved quickly, all others just go at the bottom of the way too long priority list. 😭

Considering that that report is almost a year old now..

[slow raft]

I just filed a bug report there too with a video demonstrating the problem: https://github.com/WootingKb/wootility-issues/issues/338

It really makes me wonder how often they even look at that repo tho. Pretty much no recent issues have any interaction or acknowledgement by Wooting