Clean up uses of setClientMessageEvent

In sendRestart, switch to the new setClientMessageEvent' and pass no
data, as no data are expected. Passing currentTime was confusing, as
it's only interpreted as time in some ClientMessage types.

In killWindow, it's the other way around.
This commit is contained in:
Tomas Janousek
2021-02-11 18:46:41 +00:00
parent 09425bbe43
commit 676530307b
2 changed files with 2 additions and 2 deletions

View File

@@ -133,7 +133,7 @@ sendRestart = do
xmonad_restart <- internAtom dpy "XMONAD_RESTART" False xmonad_restart <- internAtom dpy "XMONAD_RESTART" False
allocaXEvent $ \e -> do allocaXEvent $ \e -> do
setEventType e clientMessage setEventType e clientMessage
setClientMessageEvent e rw xmonad_restart 32 0 currentTime setClientMessageEvent' e rw xmonad_restart 32 []
sendEvent dpy rw False structureNotifyMask e sendEvent dpy rw False structureNotifyMask e
sync dpy False sync dpy False

View File

@@ -91,7 +91,7 @@ killWindow w = withDisplay $ \d -> do
io $ if wmdelt `elem` protocols io $ if wmdelt `elem` protocols
then allocaXEvent $ \ev -> do then allocaXEvent $ \ev -> do
setEventType ev clientMessage setEventType ev clientMessage
setClientMessageEvent ev w wmprot 32 wmdelt 0 setClientMessageEvent ev w wmprot 32 wmdelt currentTime
sendEvent d w False noEventMask ev sendEvent d w False noEventMask ev
else killClient d w >> return () else killClient d w >> return ()