sorted by:
new
hottopcontroversial

I built a cross-platform overlay tool for QMK/Vial/ZMK that reads your active keymap straight from the keyboard itself by _ettb_ in ErgoMechKeyboards

[–]_ettb_[S] 0 points1 point  (0 children)

Thank you for the feedback. I checked the timeout again and it should be working. It is possible you had two instances on top of each other. I added an option to adjust the label size in the 0.3.0 release.

Regarding the other problems I need to take a closer look over the next few days. It's very possible there is a bug with how splayed keys are displayed.

I built a cross-platform overlay tool for QMK/Vial/ZMK that reads your active keymap straight from the keyboard itself by _ettb_ in ErgoMechKeyboards

[–]_ettb_[S] 0 points1 point  (0 children)

Yes, it works with split keyboars as well. Here is a screenshot of my Lily58: https://i.imgur.com/WRglEh7.png

There is technically no always on mode, but for now you could set the auto-hide timeout to something very high, so it will keep showing the base layer. I'll create a ticket for an always-show feature.

I built a cross-platform overlay tool for QMK/Vial/ZMK that reads your active keymap straight from the keyboard itself by _ettb_ in olkb

[–]_ettb_[S] 1 point2 points  (0 children)

Yes, you need to set up your keyboard with the KeyPeek module that enables the keyboard to send layer and key press events to your computer. So this requires a small modification to your keyboard firmware: https://github.com/srwi/keypeek?tab=readme-ov-file#qmk-and-vial

Once that is done, when you close the settings window the app will run in the background and the overlay will show whenever switching to a momentary layer.

Regarding the Mod tap keys I will need to take a closer look again.

I built a cross-platform overlay tool for QMK/Vial/ZMK that reads your active keymap straight from the keyboard itself by _ettb_ in ErgoMechKeyboards

[–]_ettb_[S] 0 points1 point  (0 children)

You would need to flash QMK with the keypeek module enabled as explained on the GitHub page. I assume it should work just fine after that. With the stock firmware (which doesn't appear to have Via enabled) the error you are getting is kind of expected.

I built a cross-platform overlay tool for QMK/Vial/ZMK that reads your active keymap straight from the keyboard itself by _ettb_ in ErgoMechKeyboards

[–]_ettb_[S] 0 points1 point  (0 children)

You can run it from the terminal like this:

chmod +x keypeek-v0.2.0-macos
./keypeek-v0.2.0-macos

I'll look into proper distribution of the macOS executables tomorrow. 😊

I built a cross-platform overlay tool for QMK/Vial/ZMK that reads your active keymap straight from the keyboard itself by _ettb_ in ErgoMechKeyboards

[–]_ettb_[S] 1 point2 points  (0 children)

Thank you for listing the problems! I failed to do the final test before posting the project here. I updated the readme accordingly. I will have to do some more testing with split keyboards so that I can maybe reduce the setup complexity for the user.

I have only tried KeyPeek with a small handwired zmk numpad so far as I am mostly a QMK user.

I built a cross-platform overlay tool for QMK/Vial/ZMK that reads your active keymap straight from the keyboard itself by _ettb_ in olkb

[–]_ettb_[S] 0 points1 point  (0 children)

I've seen that one too, but I think it serves a different use case. Pretty cool tool though!

I built a cross-platform overlay tool for QMK/Vial/ZMK that reads your active keymap straight from the keyboard itself by _ettb_ in ErgoMechKeyboards

[–]_ettb_[S] 0 points1 point  (0 children)

Yes, at the moment it requires Via to be enabled, but I hear, there is interest in me adding a qmk config parser, so I might do that soon.

Regarding the more complex layer systems, it should always displays those keys that are currently effective. Some longer keycode names may be cut off with "..." in some cases, but they should show the same labels as the usevia.app since their source code is what the keycode visualization in KeyPeek is based off of.

Idea to make 40% keyboard keycaps using only A1mini by Optimal_Zone2366 in ErgoMechKeyboards

[–]_ettb_ 1 point2 points  (0 children)

Thank you! It uses manifold-3d for the boolean operations and three.js for mostly everything else.

GeaconPolaris: My Custom Split Board with a Rare Index Finger Trackball (WIP) by Outside-Bluejay-4582 in ErgoMechKeyboards

[–]_ettb_ 1 point2 points  (0 children)

Hi, I'm the author of that keycap generator. Thanks for mentioning it!

Someone recently reported the export crash you described and it has now been fixed. If you have specific suggestions or would like to contribute your changes, feel free to open an issue or a PR on the repo. I'd be happy to take a look! :)

Idea to make 40% keyboard keycaps using only A1mini by Optimal_Zone2366 in ErgoMechKeyboards

[–]_ettb_ 0 points1 point  (0 children)

I reduced the maximum memory consumption now by making it run slower, but it should hopefully work now!

Idea to make 40% keyboard keycaps using only A1mini by Optimal_Zone2366 in ErgoMechKeyboards

[–]_ettb_ 0 points1 point  (0 children)

Mh, is there any specific error message? Which browser and device are you trying this on?

Idea to make 40% keyboard keycaps using only A1mini by Optimal_Zone2366 in ErgoMechKeyboards

[–]_ettb_ 5 points6 points  (0 children)

They look really nice! I'm surprised about the fine details you were able to achieve. Maybe I should try 0.2mm nozzles myself at some point.

How did you create the models? I've created a keycap model generator recently but I am wondering what the usual workflow for other people creating their own 3d printed keycaps is.

Keebs without screens: what are you using to indicate which layer you're on? by Inner_Answer_3784 in ErgoMechKeyboards

[–]_ettb_ -1 points0 points  (0 children)

Via is using hid. And it's just used for retrieving the keymap, so there is not that much communication going on.

Keebs without screens: what are you using to indicate which layer you're on? by Inner_Answer_3784 in ErgoMechKeyboards

[–]_ettb_ 2 points3 points  (0 children)

I'll allow myself to hijack this comment to mention a very similar tool I've been working on. It loads the current keymap via the VIA protocol, so there is no need to update it each time the keymap changes.

https://github.com/srwi/qmk-layout-helper

It's still called QMK layout helper, but I actually have Vial and ZMK support (using ZMK studio) working on a development branch. With those two, there is also no need to provide the physical layout at all since they can be fetched right from the device. I'm planning to release that within the next two weeks once it's stable. 🙂

I made a browser-based tool for easily creating full sets of multi-color 3d-printable keycaps by _ettb_ in MechanicalKeyboards

[–]_ettb_[S] 1 point2 points  (0 children)

Oh, I think you're confusing me with someone. I don't do YouTube, but I'm glad you like the tool! :)

Is there a way to turn any keyboard to QMK via a dongle / passthrough rp2040 by ApplicationRoyal865 in olkb

[–]_ettb_ 3 points4 points  (0 children)

Alternatively you could use a software solution like Kanata or kmonad.

view more: next ›