More efficient Path capabilities

[pzl]

Currently creating all paths will all capabilities. This may use more resources than necessary¹ when used on simple paths. Instead, maybe take a minimum-and-build-up approach where a path is created with bare minimum capabilities, and as each function is requested (a transform, an interpolation) the capability is dynamically added before the operation.

1: ARM Mali GPU doc:

3.2.6. Set correct path capabilities

Specify what your paths are going to be used for. If VG_PATH_CAPABILITY_*_FROM or VG_PATH_CAPABILITY_MODIFY are not required, the driver can conserve memory as it can throw away the original input data.

[pzl]

OpenVG 1.0.1 spec:

At the time a path is defined, the application specifies which operations it wishes to be able to perform on the path. Over time, the application may disable previously enabled capabilities, but it may not re-enable capabilities once they have been disabled.

Should still look into using reduced-capability paths, but may need some other approach like using intermediate paths