Komari Spaghetti

I like the idea of having a makefile that does some of the work we require people to do, like auto generating `nuklear.h` and doing the docs (which I actually...

Hi. This might be something good to get in, but from the code sample it is a little hard to see what is original and what has changed. Can you...

As for Zig, `@"null"` can be used for variable, field, function and declaration names, so it is not really a problem as long as Zig's auto translation tools actually does...

Looking into it a little, `margin` seems to be the correct term for spacing outside a box (progress bar in this case). Seems there are quite a few elements where...

Here is my personal take. Nuklear is a C library, not a C++ library. I does the bare minimum to ensure that the library can compile under C++ but nothing...

Also, c++ have it easy compared to other languages when it comes to simple usage. :wink: ```c++ #include struct nk_slice { const char *ptr; size_t len; }; struct nk_slice operator...

> In general, it would be nice to see more ergonomic c++ usage. A supplementary nuklear.hpp could do that. Well, this sounds like bindings to me, which [people already maintain...

Anyways, I don't think this is to relevant for this specific PR and is something that could be added later anyways. This change would already make the library a little...

> I'm not sure I'm understanding your last two Notes bullet points. In the changes I didn't see any nk_*_label functions changed/removed? > > Also it looks like all the...

> Uneducated suggestion: some of the points raised by @rswinkle could be explained in comments in a more direct way (basically formulated as "answers" to @rswinkle's questions) instead of just...