cesss

Understood, @sp1ritCS . Looking at their licenses (OFL and GFL), I'm not a lawyer, but from what I've read they don't seem to have copyleft effects in applications that embed...

My current idea is to bake the tessellation of each glyph (I'm working with vector graphics, using tri-meshes, so I need to tessellate the glyphs paths). What I don't know...

Yes, compare the distances from the button texts to the button borders in the original NanoGUI screenshot here: https://raw.githubusercontent.com/wjakob/nanogui/master/resources/screenshot.png to your current screenshot here: https://github.com/dalerank/nanogui-sdl/blob/master/resources/screenshot1.png Don't you see that the...

Look at Radio Button 1 and Radio Button 2 for example: Don't you see they are almost touching the button edge in your latest screenshot, while in the original they...

Well, step by step. What I thought is not to port the complete example folder, because it would be a lot of work. Instead, I was thinking in porting component...

Try for example the demos with Roboto size 24, or size 32, and you'll see what I mean.

I've been trying to find the reason. It seems there are two issues: the first one is that the minimum row height automatically guessed by Nuklear is not enough when...

Found the reason: The demos are hardcoding the row height instead of leaving it as automatic. So, for the moment, I have a proper way of avoiding vertical overlap problems....

Regarding the minimum width of a widget, I searched the old repo, and found that @vurtun was not a friend of automatic layout (which is a bummer, because I need...

I think that if a row height of 0 has the meaning of "automatic height", so that the row gets automatically the height it needs for arranging its widgets, then...