Actionless Loveless

just look into existing one as an starting point, IMO for this stuff the `spec` tests would fit the most

spec means simple unit tests, something what using spawn sounds like an integration test - in that case check some tests from `tests/` directory as a guideline

i think understanding your problem would be easier if you provide some screenshots illustrating your problem and highlight specific parts of the apidoc which by your opinion are not designed...

this one i also can reproduce with standard 1920x1080 display:  

could you try to add some sort of print there to see if that event itself not being fired or activate() inside handler does nothing to that client

i wish i could help, but i banned by one super-petty moderator from arch wiki :D (official reason for breaking, sic!, all the rules at the same time, however no...

i believe it's smth what should be rather better-explained in documentation, not fixed in code

actually client name neither need to be writable if i recall x desktop spec corrrectly (and ~2 years old convo under similar ticket)

https://tronche.com/gui/x/icccm/sec-4.html#WM_ICON_NAME

@Aire-One > AFAIK, client icon_name property is readonly in our API. actually after reading the spec for both WM_NAME and WM_ICON_NAME i dont see a reason why one of them...