But it doesn’t accept that. Changing ofPoint to ofVec3f doesn’t help either.
As a fix I’m a for loop with mesh.addNormal(), but I would like to how to use previous one.
Error (active) E0304 no instance of overloaded function "ofMesh_<V, N, C, T>::addNormals [with V=ofDefaultVertexType, N=ofDefaultNormalType, C=ofDefaultColorType, T=ofDefaultTexCoordType]" matches the argument list
'void ofMesh_<ofDefaultVertexType,ofDefaultNormalType,ofDefaultColorType,ofDefaultTexCoordType>::addNormals(const N *,size_t)': cannot convert argument 1 from 'std::vector<ofVec3f,std::allocator<_Ty>>' to 'const std::vector<V,std::allocator<_Ty>> &'
no, ofPoint is an alias for ofVec3f our old vector math library. since 0.10 OF includes and uses glm for vector math. you can still use ofVec in a lot of cases mostly to keep compatibility with old projects or at least to make it as easy as possible to keep using them but it’s recommended to use glm if you are working on new projects
So math element like normals, directions, now are different from elements like points?
Are they two different classes that are meant to be kept separately, or one is a derived version of the other?
Sorry for the naive question. I didn’t find some design philosophy of OF, and some of the things seems quite different from commonly used packages for meshes and math operations, like Eigen, libigl, etc.