#Keyboard/Keypress Visualizer?

1 messages · Page 1 of 1 (latest)

golden bronze
#

I know there is some way to see the keyboard lighting on the wootility software already, but it can be kinda glitchy at times.

I'm trying to display my keyboard with its keypresses while streaming but it's not working as intended.
It would be nice to have a feature that would open a window displaying the keyboard layout with AOE for example, a plus would be for it to be customizable regardless of the current keyboard setup.

This is definitely not a necessary feature, more like a QoL addition ! 🙂

undone laurel
golden bronze
#

God I love community driven projects... blobaww

#

So basically like this, but a simpler version that you could include into the wootility software, that doesn't require a local server for the mainstream noobs 😇
Unless you're planning to add plugin support in the future?... pepe_uhm

undone laurel
#

that plugin doesnt need a local server either

#

maybe @low vessel can explain if im misunderstanding but from what i know it has a website for both general visualization and usage in OBS

golden bronze
#

"This application uses a local TCP server that must be kept running while using the website to display your values."

I installed it and it's very nice to mess with ! Btw if the dev comes around, I noticed a lil glitch upon key removal (if you right click another key too fast after deleting a key, the 2nd key disappear but is not deleted)

low vessel
#

Hey! Thanks for trying out the app. It does require a local server unfortunately as this allows the c# app to detect key presses all the time, unlike in js it can only detect when the window is focused. Is there any reason for aversion to a local server?

undone laurel
#

TIL i guess

golden bronze
# low vessel Hey! Thanks for trying out the app. It does require a local server unfortunately...

When I made that suggestion, it was more of a QoL addition to the wootility software as it's a useful feature in many others keyboard software (I previously used to capture the corsair software to display my keys), my aversion to a local server is mostly having to run it, but your app surely gets the job done ! 😄
Regardless, as a feedback for your app after using it a bit more, there's a few suggestions I have :

  • I used nohboard (https://github.com/ThoNohT/NohBoard/), which allows me to display keys from every keyboards, I was wondering if there was a way to add an option so your app could do the same (which would switch the capture between wooting only or any keyboard), in case I'm not making much sense, I could showcase a demo just let me know !
  • Another great addition to your software, would be to add labelling to the keys (on nohboard you could even use images for that).
  • It might imply a lot of work, so it's more of a question rather than anything else... Azerty layout support? 😇
  • When you used a key already in the layout, you can't add it twice, so if I want to display a key twice, it's currently impossible.
low vessel
#

Just walking home now, for your first paragraph, there was/is plans for it to be integrated into wootility but sadly delayed

#

Point 1 - wootverlay works with any keyboard if that's what u mean, just displaying on/off rather than pressure

#

For 2, do u mean renaming keys? U can rename it such as shift to an arrow ASCII character but no images yet sorry

#

For 3, you can drag the keys around to form any layout :) but in case you're looking for presents for azerty there are none soz, u are able to save your own presents into the cookies for easy access

#

For 4, umm I just assumed no one would want that haha but I could possibly change it in the future

#

@golden bronze unless azerty layout has some different keys I'm unaware of oops

golden bronze
golden bronze
golden bronze
golden bronze
golden bronze
low vessel
low vessel
#

The labelleing feature exists right now btw!

low vessel
golden bronze
low vessel
#

Wait i just tested what i thought might be the case haha - non wooting keyboards only work when wootility isnt running. I'll look into it accepting normal input when there is no wooting keyboard connected with a toggle between Wooting mode or other keyboard mode in the right click menu

golden bronze
low vessel
#

Ah right, if you press the < key on your keyboard with the additional info turned on, what number shows up?

golden bronze
#

226 for the <

low vessel
#

Rightt interesting I have not done any AZERTY testing, for me its just 54

golden bronze
#

But instead of just adding the "<", maybe you should add a second label into key modifier in order to add any keycode

golden bronze
low vessel
#

Yeah that would be cool, I also have to specify the keys in the desktop app as well though since I have a keylistener running to detect if keys are 'pressed' or 'not' as the analog SDK only does pressure levels, so green/red activeness wouldn't work

golden bronze
#

Btw, another thing I've noticed about custom presets, it saves the layout, but I don't think that's the case for color settings etc...

low vessel
#

Oh yeah i haven't done that yet soz lol

golden bronze
#

As long as you're aware 😛

#

Very last question, are you planning to implement mouse support in the future?

low vessel
#

Oh ummm I haven't really thought about mouse support too much yet since it's not really analog

golden bronze
#

Yeah it usually is a big struggle to implement, and kinda wonky at times.. D:
I'm asking this because I do mouvement gamemodes on source games and I've never found solution to display that kind of input properly on stream
Thanks for all the answer, feel free to hit me up if you need any user feedback on your app, I'd be happy to help ! 🙂

low vessel
#

Sweet, feel free to also add issues to the github for easier tracking :) thanks

low vessel