Pass 0 to setClientMessageEvent where appropriate

Stop pretending it has anything to do with time, it's zero, and it's not
being read anywhere, we're passing the parameter only because
setClientMessageEvent needs one. We should switch to
setClientMessageEvent' and pass no data, but that would move the X11
dependency lower bound.
This commit is contained in:
Tomas Janousek 2021-02-11 18:48:36 +00:00
parent a7bb1a776a
commit eb752b15d8
2 changed files with 2 additions and 2 deletions

View File

@ -41,7 +41,7 @@ startTimer s = io $ do
a <- internAtom d "XMONAD_TIMER" False a <- internAtom d "XMONAD_TIMER" False
allocaXEvent $ \e -> do allocaXEvent $ \e -> do
setEventType e clientMessage setEventType e clientMessage
setClientMessageEvent e rw a 32 (fromIntegral u) currentTime setClientMessageEvent e rw a 32 (fromIntegral u) 0
sendEvent d rw False structureNotifyMask e sendEvent d rw False structureNotifyMask e
sync d False sync d False
return u return u

View File

@ -48,7 +48,7 @@ sendCommand addr s = do
m <- internAtom d s False m <- internAtom d s False
allocaXEvent $ \e -> do allocaXEvent $ \e -> do
setEventType e clientMessage setEventType e clientMessage
setClientMessageEvent e rw a 32 m currentTime setClientMessageEvent e rw a 32 m 0
sendEvent d rw False structureNotifyMask e sendEvent d rw False structureNotifyMask e
sync d False sync d False