diff options
| author | Isaac Freund <ifreund@ifreund.xyz> | 2021-09-18 18:25:21 +0200 |
|---|---|---|
| committer | Isaac Freund <ifreund@ifreund.xyz> | 2021-09-18 18:45:30 +0200 |
| commit | b8ebbc29cf42a36e97666bf9757a9bc354e31925 (patch) | |
| tree | 5daaf5ead259075d19368e90a7fe24291b14230c /protocol | |
| parent | ab55ab8fc2a7f795ec586ad829d040a9820a4486 (diff) | |
| download | river-b8ebbc29cf42a36e97666bf9757a9bc354e31925.tar.gz river-b8ebbc29cf42a36e97666bf9757a9bc354e31925.tar.xz | |
xdg-toplevel: fix configure serial checking
Currently if another configure is in flight after the one we are
tracking the serial of and the client acks the second configure as well
(or only the second configure) before committing, we will never realize
the configure we are tracking has been acked.
Instead, listen for the ack_configure signal and set a bool that we can
check on surface commit.
This probably isn't an issue that would actually be hit by well behaved
clients as river doesn't send redundant configure events. However,
having correct code is always better even if it's slightly more complex.
Diffstat (limited to 'protocol')
0 files changed, 0 insertions, 0 deletions