Ultimate Wootility feature wishlist

[valid elk]

This is a small list I made withing the first week of owning my 60HEv2 & forgot to post.
Wootility is such a great software but it's been in development for so many years now it's kind of surprising some of these aren't a thing yet.

-More characters & option for "Remap" feature (e.g. Umlaute Ö, Ä, Scrollwheel Up/Down)

-Select all buttons in "RGB Settings" & Keys staying selected while choosing a color so it updates in real time (Every keyboard software I've ever used does it that way, having to draw over the keys to change colors is super inconvenient imo)

-Pressure sensitive RGB spectrum (Select 2 colors, RGB will smoolthly fade between the two throughout the keypress)

-"Alternate Behavior" for Snappy Joystick

-Hotkey to disable Rappy Snappy & Snappy Tappy (so you won't have to waste a profile slot. When the Wooting background service is able to detect games in the future this could also be auto deactivated in games where it's not allowed.)
Right now it could be implemented similar to the FN Layer Key lock remap.

-Most importantly: Pressure sensitive Display Brightness & Volume adjustments
(I honestly have no idea why this isn't a thing yet, I have been missing a knob on my keyboard & this would be such a great & obvious way to deliver a similar feel on an analog keyboard.)

[floral glade]

Dont take this as a deny but just as explanations.

i can comment on 2 of these:

1. thats not how remapping scancodes work. you are remapping character output with the remap.

To make a more complex topic short: every ISO keyboard and ANSI keyboard has scancodes which dont change no matter what "language" of keyboard you buy. The reason windows asks for the keyboard language is so it can map the output characters to the printed ones on the keycap. Keyboards themselves dont know what an A or an ö is.
If you set your keyboard layout to US English on Windows for example the keymapping doesnt even have an Ö you can map anywhere on the keyboard.

Theres also the issue that outputting something like Ö works different on MacOS/Linux than on Windows so if youd remap it to Ö you either have to also set your keyboard to the OS you use OR accept it only works on 1 OS.

We have some ideas on how to fake this which would require the background program but no promises it will ever come or when it would come if we decide to work towards this.
(Probably more likely wed release macro functions so people can make their own macro keys that do this)

2. Someone coded their own pressure volume control years and years ago at this point. They said theyd release it but never did despite confirming they got it to work. I assume it just wasnt an actually usable feature.

I dont know what way of doing this they went with but the only 2 I can think of are below.

• Youd still need 2 keys to adjust volume where 1 enters volume adjustment mode and the other controls which level you set it to where you have to hold it in place and let go of the first key.
• PWM style spam the volume down or up key more often and faster the deeper you press.

If you have more ideas on these 2 (or other things) we would be happy to hear about it

The other suggestion all make sense to me and I wonder what our keyboard team thinks about working on those or planning to work on them at some point

[valid elk]

but why does all of this work with via compatible keyboards (https://www.usevia.app/)

As for the volume control I'm not sure what the best way to implement would be. I'd want it to work exactly like I currently use my volume control (just volume up & down on FN Layer 1). Maybe instead of having the key constantly activated it could keep clicking in various intervals depending on how deep a key is pressed.

[floral glade]

idk if id call it works as it uses a quite hacky way to accomplish this. keyboards have no way to tell which OS they are connected to. there is differences in how each OS enumerates HID devices but this difference can change at any point in time and could also be gone at any point in time

we basically try to build on established things that will most likely keep working for the longest time possible. this is also why theres no custom drivers and all devices we have our keyboard show up as are standard OS included things. This is also why we try to do as much as possible without software required and try to accomplish as much as possible in the keyboard itself. (of course some things will always need software)

[valid elk]

I really hope we‘ll get the ability to deactivate illegal features ^^

interested to see what the background service will bring