Results 36 comments of Sergey

It will be good to handle also group visibility

It is possible ![2018-07-23 23 08 19](https://user-images.githubusercontent.com/485515/43100258-712952ea-8ecd-11e8-8836-2f348ba3a285.png) Sorry for not full codes. It is a copy from radialGradient but replacing one line ~~~ - gd = sqrtf(gx*gx + gy*gy); +...

And a syntax radialGradient -> conicGradient

![2018-07-25 7 21 43](https://user-images.githubusercontent.com/485515/43180074-bfd41d82-8fde-11e8-9307-f1c6724c6645.png)

Why not use float arithmetics?

There are two questions: 1. Make rasterizing not only with tx,ty,scale, but with full matrix including rotation. 2. Correct calculate image box after rotation to fit into view box. I...

It is resolved with pull request #103

Such picture? ![2018-08-15 19 24 52](https://user-images.githubusercontent.com/485515/44159741-094d6700-a0c1-11e8-9492-6ce2f8134cd7.png) :)

OK. One moment else. Should we perform parsing "transform" after parsing "x" and "y" in nsvg__parseAttr? The order is significant.

O, I see you already said this "Also, transforms attributes need priority for (and possible others), but they are currently parsed in the order they are found." Somehow reorder attributes?