You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since some messages such as "Offsets thread is finished.", "Received header for stream ", etc, are being outputted from multiple threads, they show up looking a mess inside a console window, especially when one has multiple LSL streams running. Perhaps you can lock a new "output mutex" when doing calls to cout and cerr to make sure the messages look nice.
The text was updated successfully, but these errors were encountered:
So far I haven't had that issue personally, but I mostly have less than 10 streams and maybe my libstdc++ is less prone to it than others.
My suggestion: create a logging function (void log(const std::string& msg)) that locks a mutex internally. That way we can also enable callbacks to a logging function later on more easily.
Is this something you'd be comfortable preparing a PR for?
Yep that's exactly what I was thinking. I can do a PR for it pretty soon. For reference this messy message issue was seen on multiple different Windows 10 machines in both CMD and PowerShell outputs.
Since some messages such as "Offsets thread is finished.", "Received header for stream ", etc, are being outputted from multiple threads, they show up looking a mess inside a console window, especially when one has multiple LSL streams running. Perhaps you can lock a new "output mutex" when doing calls to cout and cerr to make sure the messages look nice.
The text was updated successfully, but these errors were encountered: