Mikko Mononen

Take a look at the readme, it lists the OpenGL state the renderer changed during rendering. https://github.com/memononen/nanovg#opengl-state-touched-by-the-backend So yes, NanoVG may change the blend function. On Tue, Dec 31, 2019...

I hope that we get enough maintainers so that it might take an hour or two a week. For features and bigger code reviews it might be more. > On...

It's "oldskool" trick to create variable length array without extra pointer and alloc. On Sat, Nov 16, 2019 at 4:41 AM Aaron Franke wrote: > It seems like a bug...

Tail is used to speed up insertion to the linked list during parsing, not needed later. Sent from my iPhone > On 22 Aug 2018, at 21.58, Sergey wrote: >...

The tail is only needed during parse (it makes things faster). If you do your manipulation after parse, then you just walk the linked list to find the tail.

NanoVG will change some OpenGL state, which you will need to manually reset. See https://github.com/memononen/nanovg#opengl-state-touched-by-the-backend

The anti-aliasing is inspired by the recent signed distance field rendering stuff, and this old article from graphics gems 2: https://developer.nvidia.com/gpugems/GPUGems2/gpugems2_chapter22.html I have picked up most of the curve handling...

The code should handle removing the hash, looks like a bug. Can you make a separate issue about that with the above example file? If the linear gradient is positioned...

I impemented percent coordinates, and the gradients should work as expected. Can you check and let me know how it works for you?

This should allow you to get the the screen space start and end points: ``` C static void xformInverse(float* inv, float* t) { double invdet, det = (double)t[0] * t[3]...