Rob Loach
Rob Loach
The Font Loading example might be a good place to test out using vector for construction and deconstruction of these data types; https://github.com/RobLoach/raylib-cpp/blob/master/examples/text/text_font_loading.cpp
Is this anything that could be pushed upstream to raylib? Or would an update to raylib 3.7 help?
A few options here... 1. Use `raylib::Model* model;` instead... construct and delete at ObjectName destruction 2. Pass `const char* path` in as part of the ObjectName constructor I'm not sure...
Mind submitting a Pull Request? Others may be interested in it too. I'd love to see what you're proposing.
Quick thought... Would an initializer list for this help here? https://docs.microsoft.com/en-us/cpp/cpp/constructors-cpp?view=msvc-170#member_init_list ``` cpp class ObjectName { public: ObjectName(const std:string& modelFile); ~ObjectName(); void Load(const char* path); void Draw(raylib::Vector3 pos); private: raylib::Model...
Thanks @bensuperpc! Should we instead compare their magnitudes instead? Comparing their individual coordinates may not get the desired results.... In raylib, the lengths.
Which version of node are you using?
``` ERR! OMG CMake executable is not found!!!! ``` OMG!!!! Make sure cmake is installed! I'll update README.md with that note :smile:
Good question... There was a CleanUp process in the old bindings. Perhaps the new ones are missing that clean step.