[10:30] <alan_g> alf_: Just checking my thinking... there's no way for a server based on Mir to detect that the server is about to shutdown? (Beyond hooking signals, and policing its own use of stop())
[10:32] <alf_> alan_g: I don't think so, but I guess it depends on what "about to shutdown" means. What's the use case?
[10:34] <alan_g> In miral I want to exit an "in process client" before the server closes the connection
[10:34] <alan_g> So SIGINT, or Ctrl+Alt+BkSp, or ...
[10:37] <alf_> alan_g: Would adding a ServerStatusListener::about_to_stop and calling it just after the mainloop exits in DisplayServer work for you?
[10:39] <alan_g> alf_: I think it would be better if it happened before the mainloop exit. But I was really checking I wasn't missing an existing method.
[10:41] <alf_> alan_g: there isn't an existing method I am aware of
[12:10] <alf_> alan_g: I am thinking of making a few changes to the tiling window manager in miral, but wanted to check with you first. The core of the changes is that every surface always takes up exactly the space provided by the tile (as long as the app itself allows that, not sure we support max/min sizes?). With multiple tiles, resizing a tile/surface will just give more space to the others.
[12:27] <alf_> alan_g: A concern I have is that this will start to increase the complexity of the tiling WM and perhaps we want to keep it more simple as an example, rather than a full blown tiling WM?
[12:57] <alan_g> alf_: Please go ahead - I want the WMs in Miral to be serious efforts that test the API, not proof-of-concept examples.