refactor: New LogWidget to handle log output in the mainwindow - #8877

Just curious, what's the handle about? Might be confusing for users.

I clicked the 'X' on macOS, and it crashed.

Oh shit, this is in master. Raised a new bug:

• Reconnect from client causes SIGABRT #8910

Edit: Fixed in:

• fix: Use correct log function for process exit status in onProcessFinished #8911

The handle is there if we allow resize of the dock area .. If we allow undocking or moving you can move it that way

Should we just make its own dialog? and not let it dock?

Edit: to remove that handle the dock needs to be a fixed vertical size so we have to do all the resize manually to avoid that . I would suspect GNOME is gonna hate that.. Another option is to allow the user to move the dock around , to do this we must let the user always resize the window, so we have more chances for it to not log great if you pull out the log etc. I've been playing with a 3rd option allowing the user to float then redock the log but this is not working great due to our resize code. I am all for making it a floating dock that looks like a dialog , i would make it its own dialog (not a dock) but we need the log reading happen in main window until #8879

I do not think the log is critical feature for most users. As we do communicate most errors via dialogs from the GUI.

GNOME's gonna GNOME...

Both are caused by Alt+Tab after changing the log visibility.

Edit: It only happens the 1st time you Alt+Tab after toggling log visibility. After that, it doesn't happen again. Seems like some kind of race condition or state/sequence bug related to resize. I can confirm this only happens on GNOME, never happened on KDE.