It’s up to you, but if the interface is supposed to be even a little bit serious, you’d better think a few more times.
At least KOUI has more possibilities in design.
Although it all depends on the task.
When ZUI crashes every once in a while, you will remember my words
Do you mean whether Armory uses any or whether they support them?
Yes, there’s a section in the Armory manual relating to Zui.
It’s very unstable. However, you’re still using armsdk 2022.08, correct? I’m going to be honest, every bug you report that isn’t on the latest release makes things harder for developers, as you’re issue may already be solved and dependencies change time to time.
Actually, I believe you did say you were using Zui.
You quoted me saying I “decided to try zui.”
Followed immediately by “I’ll probably end up using feathersui”
If trying out something means using it in all contexts, in your view, I’ll thank you for telling me a little about yourself.
However, in the context used, I was not using zui, nor planned on using it, as implied by @kaiwas.
I checked it out. It didn’t check out.
You don’t have bad Fridays, do you?
No, Khamake expects .ttf files for fonts (source), unless of course you write a .dat file reader that can convert the file contents into a kha.Font object.
FeathersUI is for OpenFL and not for Kha, so it will not work with Armory unless you rewrite a lot of it. Btw, if you use Armory2D, you already use Zui even though Armory just calls it a “Canvas” (regarding the discussion above).