SVGKit does not work exactly as I need. Although I have to say that this is well done. There are other resources that I have found, and I will leave them here for future reference if anyone stops at this post and is looking for a solution.
Converting SVG Paths to Objective-C Paths Good for simple paths; strokes and fills can be manipulated later using protocols. Complex paths get confused.
SVGKit Good for creating images and animating them later in the program. However, one cannot manipulate strokes, bays, and paths.
Opacity You can export as source code, so you have more control over the strokes, paths and fillings. As the path becomes more complex, manually managing the code is more difficult. Another problem - at the time of export, the program adds code-dependent codes. It can be a pain to go through about 300 lines of code to fix it so that it does not depend on permission. The end product would not be mixed, and they could be manipulated by protocols. Layers are CGLayers, not CALayers.
source share