dumblob

It seems to boil down to the fact, that styling in Nuklear is still kind of preliminary and to put it bluntly, there are places in the library, where **some**...

Code has higher priority, but wiki would be also nice :wink:.

>a combobox in itself is only an aggregation of simpler parts, like buttons and contextual panels? Yep, that's one thing. Another thing is, that everything which "overlaps" anything else is...

Modify `src/nuklear.h` and then follow instructions in `src/Readme.md` which will automatically generate `nuklear.h`. Don't forget to change version accordingly.

Hi, thanks for the PR. Before going further, could you please change the source files for "paqing"/amalgamation (see `src/`) and also bump the version accordingly?

Sorry for that, I can understand your frustration - feel free to put the warning either to README (e.g. to a section "how to contribute") and/or to the very top...

See https://github.com/vurtun/nuklear/issues/283 , https://github.com/vurtun/nuklear/issues/74 , https://github.com/vurtun/nuklear/issues/123 .

Look up some existing bitmap font and use it. That should be the easiest, proven to be readable and in the end gives the opportunity to use other characters in...

You can try to use `nk_draw_list_stroke_poly_line()` - see `nuklear.h` for parameters and "examples of its usage": ``` case NK_COMMAND_TRIANGLE: { const struct nk_command_triangle *t = (const struct nk_command_triangle*)cmd; nk_draw_list_stroke_triangle(&ctx->draw_list, nk_vec2(t->a.x,...

>@dumblob You code not working Please read again what I wrote - `see nuklear.h for parameters and "examples of its usage": ...` (do you see the suggestion to read the...