Usage of MessageLog in non-ui threads is tricky and need to be carefully managed to avoid flushing memory on the wrong thread. With this change direct usage of MessageLog in the analysis engine is removed and replaced with a callback system which allows the user of TraceAnalysis to implement display of the messages themselves. In the case of InsightsManager this means queuing up the messages in analysis session and regularly polled from the UI thread.
#rb ionut.matasaru
#jira UE-185528
[CL 26087858 by johan berg in 5.3 branch]
We have previously relied on UE_LOG messages to indicate problems in analysis. This change converts those log messages to use MessageLog functionality which is routed to a visual log representation inside the application (but also the log file).
Additionally adds functionality to show the Insights log windows when ever (new) errors are encountered.
#rb ionut.matasaru
#jira UE-154022
#preflight 63c91aa80225f00e14758d19
[CL 23771338 by Johan Berg in ue5-main branch]
#rnx
#rb none
#ROBOMERGE-SOURCE: CL 10869240 via CL 10869516 via CL 10869902
#ROBOMERGE-BOT: (v613-10869866)
[CL 10870584 by ryan durand in Main branch]
