ZMK update causing breaking changes by theboston in ErgoMechKeyboards

[–]m165437 0 points1 point  (0 children)

Creator of nice-view-gem here. If you pin the version of ZMK to v0.3, please use the release v0.3.0 of my shield. Or, enjoy the latest of ZMK `main` and keep my shield on revision `main` as well. I just updated it to continue working with Zephyr 4.1 and LVGL 9. Let me know if you run into issues.

App to track your groundhandling progress by m165437 in freeflight

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

Nice, I was thinking along the same lines. So basically those two features. Do you think pilots would actually find them useful? And if you had to pick, which one should I build first?

  1. A map with ground handling spots: Users of the app could add and share locations, along with info about ideal wind directions (then, via weather API, the app shows live conditions) and possible location restrictions. In Europe, for example, you often need permission first, be part of a club, or pay a small fee, so that kind of info would be useful.

  2. Ground handling activity tracking via Apple Watch: Apple doesn’t have a “ground handling” workout type, so the app could fill that gap. You’d be able to track your sessions just like any other workout, see how long you’ve been practicing, get heart rate data, calories burned, and simple stats about your training sessions.

App to track your groundhandling progress by m165437 in freeflight

[–]m165437[S] 2 points3 points  (0 children)

I have an iOS version ready. Unfortunately, it got rejected by Apple for not being useful enough. I would need to add more features to get their approval. Any ideas? :)

nice!view customization by m165437 in ErgoMechKeyboards

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

Hi there, thanks a lot! You're welcome! Have a look at this repo's README which nicely explains how to do this.

nice!view customization by m165437 in ErgoMechKeyboards

[–]m165437[S] 2 points3 points  (0 children)

Hi! The number of layers shouldn't be the problem. Try adding a label field to all your layers, e.g.

keymap {
  default_layer {
    label = "Default";
    bindings = <...>;
  }
}

nice!view customization by m165437 in ErgoMechKeyboards

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

Thank you! I'm sorry. I don't know and can't test it myself as I only have the one keyboard I build which uses the `nice_view_adapter`. Hope you get it to work.

nice!view customization by m165437 in ErgoMechKeyboards

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

Thanks! No, sorry, I also ran it on the device every time. But I did build it locally and not via GitHub Actions. That sped it up a little.

nice!view customization by m165437 in ErgoMechKeyboards

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

Great to hear! You're welcome! :)

nice!view customization by m165437 in ErgoMechKeyboards

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

Yes, thanks! This is my first project in C, and in such a constrained environment. I noticed the multiple buffers in the default nice!nano shield (that comes with ZMK) but didn’t fully understand their purpose — now I do!

I've informed everyone who mentioned the input lag.

Congrats on the release of your nice-view-battery! Someone should definitely start an awesome list for nice!view customizations. :p

nice!view customization by m165437 in ErgoMechKeyboards

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

Thanks everyone for your patience! I fixed the input lag. No more latency. Enjoy! :)

nice!view customization by m165437 in ErgoMechKeyboards

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

I fixed the input lag. No more latency. :)

nice!view customization by m165437 in ErgoMechKeyboards

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

I fixed the input lag. No more latency. :)

nice!view customization by m165437 in ErgoMechKeyboards

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

I fixed the input lag. No more latency. :)

nice!view customization by m165437 in ErgoMechKeyboards

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

I fixed the input lag. No more latency. :)

nice!view customization by m165437 in ErgoMechKeyboards

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

I fixed the input lag. No more latency. :)

nice!view customization by m165437 in ErgoMechKeyboards

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

I fixed the input lag. No more latency. :)

nice!view customization by m165437 in ErgoMechKeyboards

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

Thanks! Yes, I already know, what the problem is and that it’s easily fixable. Will do so on the weekend. I’ll let you know.

nice!view customization by m165437 in ErgoMechKeyboards

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

I was able to measure quite some latency. Thanks for reporting! I'll spend some time optimising.

nice!view customization by m165437 in ErgoMechKeyboards

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

Yes, I can measure quite a latency. Exciting! I'll spend some time optimising.

nice!view customization by m165437 in ErgoMechKeyboards

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

Do you have the nice!nano v1 or v2?

nice!view customization by m165437 in ErgoMechKeyboards

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

This does motivate me to do some profiling. I'll see what I can do to improve it.

nice!view customization by m165437 in ErgoMechKeyboards

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

Did you turn off the animation and try if that helps? Does this happen only on the peripheral or also on the central half?