You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The app's current feature set is functional and does what many people need at a basic level, but knowing many people use custom behaviors like mod-morph, combos, macros, and conditional layers, it'd be ideal to make that configurable in ZMK Studio.
I'm not sure if this isn't here yet for technical limitations, or if it's feasible but needs design, if it's the latter then I think this could be solved by adding making separate pages for managing each of these actions. Entries for "Combos," "Behaviors" etc. pages could be added to the sidebar, above the layers section. As far as each page's UX flow, I think this tool's UI is a good start for how things can be handled.
That's just some off-the-cuff suggestions on how to handle UI though, so I'm not sure what's actually doable yet, but hopefully this feature request can get us in the direction of supporting these features.
The text was updated successfully, but these errors were encountered:
That's great to hear! I unfortunately don't know how much actual code I can contribute since I'm not familiar with Tauri, but I'll have to give it a look in December. In the meantime, let me know if there's anything I can do to help in terms of documentation or other contributions!
The app's current feature set is functional and does what many people need at a basic level, but knowing many people use custom behaviors like mod-morph, combos, macros, and conditional layers, it'd be ideal to make that configurable in ZMK Studio.
I'm not sure if this isn't here yet for technical limitations, or if it's feasible but needs design, if it's the latter then I think this could be solved by adding making separate pages for managing each of these actions. Entries for "Combos," "Behaviors" etc. pages could be added to the sidebar, above the layers section. As far as each page's UX flow, I think this tool's UI is a good start for how things can be handled.
That's just some off-the-cuff suggestions on how to handle UI though, so I'm not sure what's actually doable yet, but hopefully this feature request can get us in the direction of supporting these features.
The text was updated successfully, but these errors were encountered: