LabRecorder should warn users when no clock_offsets are being recorded

[dmedine]

I was thinking about @sahin-ozsoy and the clock_offsets not being recorded problem today (https://github.com/sccn/labstreaminglayer/issues/329#issuecomment-411084342).

This has sometimes happened to me even on a local host---although I didn't realize at the time that this was the problem because it only happens when I run a particular BCILab experiment and I thought it had something to do with BCILab.

I don't know why this is happening in my case, but it would be nice if LabRecorder could warn me if this was occurring. I think somebody proposed this feature already somewhere else. This would be a good project for the upcoming LSL workshop in Delmenhorst!

[tstenner]

More general: establish a way to display log messages?

[dmedine]

Yes.

…

On 08/10/2018 07:59 PM, Tristan Stenner wrote: More general: establish a way to display log messages? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/sccn/labstreaminglayer/issues/331#issuecomment-412159680>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADch7tWCvKEF8wSXAoDdhdNs3IrfJNsGks5uPcoQgaJpZM4V1vwO>.

[cboulay]

This feature was added by @tstenner to the labrecorder subrepo here: labstreaminglayer/App-LabRecorder@1920214

The work is done. As soon as we finish the repo migration then it'll be an included feature. So I'm closing this issue.

(This does not mean that the clock offset problem is fixed)