Closed kangz12345 closed 1 year ago
At some point the log viewer's curser position falls behind, so since then the logs are printed in the middle of the previous logs. For example,
[time0] log0 [time1] log1 [time3] log3 # <-- something happened between time2 and time3 [time4] log4 ... [time2] log2
Log curser should always be after the most recent log message.
Steps to reproduce the behavior: Not identified. Maybe exception or thread issue...?
I found the cause: we need to reset the cursor position to the end before inserting the log message. The cursor position is changed by user's mouse click.
Describe the bug
At some point the log viewer's curser position falls behind, so since then the logs are printed in the middle of the previous logs. For example,
Expected behavior
Log curser should always be after the most recent log message.
To Reproduce
Steps to reproduce the behavior: Not identified. Maybe exception or thread issue...?