Actionless Loveless

if i press 5 it shows separately info for gpu 0 and if 6 - for gpu 1 but then this detailed info is hidden - in the overview it...

thanks a lot! just tested that it works: 

``` > [R] retry build > [p] PGP check skip > [c] checksums skip > [f] skip 'check()' function of PKGBUILD > [n] skip 'prepare()' function of PKGBUILD > [i]...

please include your test app (https://github.com/awesomeWM/awesome/issues/4035#issuecomment-3488255106) in a similar way how xeyes is being tested example of test app built for test: https://github.com/search?q=repo%3AawesomeWM%2Fawesome%20test-systray.c&type=code

also speaking of tests, i also see some of the existing ones are failing

unlike xeyes, your case actually testable - you could return specific exit code in your app if it being clicked in that shaped surface - and assert in test for...

(and also test that when clicked outside of area - it not registers input, e.g. not exiting with that code)

there are plenty of other tests who simulate clicks, here's the most canonical example: https://github.com/awesomeWM/awesome/blob/bc57f0ff3678f71a09f919019677e4192533f713/tests/test-wibox-shape.lua#L51-L68

there is `count` function argument which is used for async tests, see here for example: https://github.com/awesomeWM/awesome/blob/master/tests/test-spawn.lua

> Also, how would I detect that the window was not clicked? by placing wibox **below** the window and catching or not catching the click on it, and double-checking afterwards...