Nitpicker's screen mode is the bounding box of all capture clients. A display driver is a capture client. In situations where the display driver is the only capture client, a restart of the driver yields a temporary situation where no capture client is present and the bounding box becomes empty. This prompts all GUI client to adapt to the temporary (and useless) intermediate mode just to adapt again to the proper mode once the driver is up again.
To avoid the intermediate visually displeasing states, nitpicker should better retain the information of the last capture client to be reported as long as no capture client exists.
nfeske
commented
2 weeks ago
Nitpicker's screen mode is the bounding box of all capture clients. A display driver is a capture client. In situations where the display driver is the only capture client, a restart of the driver yields a temporary situation where no capture client is present and the bounding box becomes empty. This prompts all GUI client to adapt to the temporary (and useless) intermediate mode just to adapt again to the proper mode once the driver is up again.
To avoid the intermediate visually displeasing states, nitpicker should better retain the information of the last capture client to be reported as long as no capture client exists.