In GitLab by @AnastasisGeorgoulas on Apr 11, 2019, 17:35
Low priority.
Logging is enabled from the slicelet, but all messages are logged in the main Slicer log (https://www.slicer.org/wiki/Documentation/4.10/SlicerApplication/ErrorLog). This happens even if we explicitly set up the logging to write to a file. It would be nice if we can get a separate logfile with messages from the slicelet and the associated modules (workflow, functions).
In GitLab by @ThomasDowrick on May 17, 2019, 13:23
I've added a QEditText to the main window, to which I have started printing various status/info messages. This might be sufficient for slicelet-level logging?
In GitLab by @AnastasisGeorgoulas on Apr 11, 2019, 17:35
Low priority.
Logging is enabled from the slicelet, but all messages are logged in the main Slicer log (https://www.slicer.org/wiki/Documentation/4.10/SlicerApplication/ErrorLog). This happens even if we explicitly set up the logging to write to a file. It would be nice if we can get a separate logfile with messages from the slicelet and the associated modules (workflow, functions).