Function Frame::doResize(bool left, bool x, bool top, bool y) will invoke a XPutBackEvent() when it is done. My question is... why?

One arising problem is when you have a configuration set like this:

//Display root meny when clicking on the background

      ButtonRelease = "1" { Actions = "ShowMenu Root" }

If resizing is done also via button 1, eg:

      Motion = "1" { Threshold = "4"; Actions = "Resize" }

Then whenever you resize a window by dragging its border, the last ButtonRelease which stops the process will also be re-handled, thus invoking the menu after every resize (unless the cursor at the end happens to be in the client or in the border, which isn't very frequent).

What is the point of putting back the event in the queue? I thought it might be to let the client receive the buttonRelease event, but some testing reveals that the client won't even receive the buttonPress event when it has been grabbed by PekWM already (even if no Motion action is triggered).

So it should be safe to remove, non?