Mikko Mononen

`fx,fy` should be in the local coordinates of the gradient. So if you multiple the `fx,fy` by the `t` matrix in above code, you should get the focal point in...

You should use matrix-vector multiply, see `nsvg__xformPoint`, where `fx,fy` is the point. I think there's a problem with parsing too: https://github.com/memononen/nanosvg/blob/master/src/nanosvg.h#L864 should be: ```C grad->fx = (fx - cx) /...

Good! Would you min making a pull request for the parser fix?

@olilarkin nanovg uses one shader for all fill types and there's if statement choosing which fill type to use. In case of solid fill, there's no texture bound to unit...

The GL backend is a bit special, as it follows the one-header-file library model (idea stolen from the stb_\* libraries). The idea is that in one file you define `NANOVG_GL_IMPLEMENTATION`...

`#define NANOVG_GL3_IMPLEMENTATION` should be in the implementation file not in header. On Sat, May 25, 2019 at 8:06 PM X.ZhaoMa wrote: > @memononen > Could you explain it a bit...

User units and px should behave the same. Setting DPI to anything else than 96 does not really make sense. That cm thing sounds odd. I changed the `nsvg__convertToPixels`to following:...

Yes, I have latest from master branch.

If the input file units are in "mm", and you pass in "mm" to parse, then they should come out as is. DPI comes to play when you convert pixels...

Thank you for the fix!