LGUG2Z c4d62fc4f6 feat(wm): run orphan reaper in a dedicated thread ...

Until now the orphan window/container reaper has always run on every
WinEvent. Unfortunately Windows Terminal does not sent a WinEvent when
it is closed.

This is a problem for the new border_manager module which draws and
destroys borders based on notifications sent to it after WinEvents and
SocketMessages have been processed.

Since Windows Terminal is not sending a WinEvent on close, this means
that user interaction is required to remove the ghost border that gets
left behind.

This commit starts a separate thread for the reaper where it runs once
every second in a loop.

This is quite wasteful and definitely not something I wanted to
implement, but a temporary solution is needed given the popularity of
the buggy application in question.

An issue on the Windows Terminal tracker has been opened here:
https://github.com/microsoft/terminal/issues/17298

2024-05-21 19:27:58 -07:00

..

src

feat(wm): run orphan reaper in a dedicated thread

2024-05-21 19:27:58 -07:00

Cargo.toml

feat(wm): add monitor reconciliator module

2024-05-19 06:26:45 -07:00