Conversation
…eem to do anything
…cker was last detected
|
I get build errors without those changes
It is just super weird to use drawAxis like that. Normally the axis is used to mark the orientation of the object being tracked, just check any OpenCV example that uses it: The axis is on the center of the tag, with the Z axis pointing outwards. What use is to have the axis lag behind (or overshoot) during movement potentially left being floating in empty space? For the purpose of displaying the position from the driver it makes more sense to draw a small circle, which I do in 57499c2.
Probably would be better, yes.
The driver then does this: And then if you read the definition for assiging a It's just one byte. Just keep the null byte at the end for safety. |
What build flags are you using? there are some utf8 handling changes that have a mess of build flags to attempt to fix the old way wxWidgets did this, for example the std::string constructor for wxString does not work with utf8. the U8String class I created is just a wrapper around std::string, and has a conversion operator that calls the correct utf8 conversion function before becoming a wxString.
The driver IPC code shouldn't assume theres a null byte, but I agree adding it is fine for safety. Ill end up copying the IPC library in ATT over to the driver eventually. |
|
Which changes should I prioritize so you can start using master? |
Could start by fixing this crash that happens as soon as a tracker is detected while connected to SteamVR (this happens on the current master branch without any other changes): |
No description provided.