If it’s so recommended to use this way, why not changing the IDE to recommend those things on the…
AndroidDeveloperLB
1

If it’s so recommended to use this way, why not changing the IDE to recommend those things on the fly?
Even importing an SVG should have let us choose which output files should be generated (including PNG)

When importing SVGs the only option is to generate a VectorDrawable so i’m not sure what choice you want? Generating PNGs from VectorDrawables is an app wide decision, not per asset and as explained in this article isn’t really needed any longer now that the AndroidX backport is so capable.

And what is this “ fillType=”evenOdd”” ? Where does it get used? What does it mean that we can’t use it on some cases?

Did the read the details I linked to when introducing this topic:

  • Both nonZero and evenOdd path fillTypes —the two common ways of defining the inside of a shape, often used in SVGs (evenOdd added to platform impl in API 24)

If you can’t use it, then paths may render incorrectly i.e. a path created with an evenOdd fillType rendered without this support may look wrong.