At the moment raylib::Vector4::Multiply (and other methods) use Quaternion math, while the data structure of a Quaternion is identical to a Vector4 (an alias in raylib's headers actually), the logic is very different. QuaternionMultiply is very different from Vector4Multiply. Decoupling them (and making raylib::Vector4::Multiply use Vector4Multiply) will however suddenly break existing code relying on raylib::Vector4::Multiply (and others)
Another solution would be to add additional methods for actual Vector4 math... but thats even worse in my opinion.
Will send a PR for #367 after this is resolved.
At the moment
raylib::Vector4::Multiply(and other methods) use Quaternion math, while the data structure of a Quaternion is identical to a Vector4 (an alias in raylib's headers actually), the logic is very different.QuaternionMultiplyis very different fromVector4Multiply. Decoupling them (and makingraylib::Vector4::MultiplyuseVector4Multiply) will however suddenly break existing code relying onraylib::Vector4::Multiply(and others)Another solution would be to add additional methods for actual Vector4 math... but thats even worse in my opinion.
Will send a PR for #367 after this is resolved.