I've got a wxApp (in windows) that would like know when the user stops resizing
a frame. I don't want to use a EVT_SIZE timer approach, but instead I thought
the frame could catch the mouse clicks on the frame border which start and stop
the resizing process. I have tried 2 approaches to catching this event:
0. Catching wx.EVT_SIZE and wx.EVT_MOUSE_EVENTS in the frame, and maintaining a
state variable self.resizing to indicate whether the frame is currently being
resized. Then in the wx.EVT_MOUSE_EVENTS handler if I see event.Up() and
self.resizing, that means the user has stopped resizing. This didn't work
because it looks like no mouse events are generated when frames' borders are
clicked. Is that expected behavior?
1. Catching wx.EVT_SIZING in the frame. I thought this event would give me the
info I needed to determine when the user was starting and stopping a resize
process. From what I can tell, it looks like this event is exactly the same as
wx.EVT_SIZE, except that it additionally catches the frame border clicks. I
compared the wx.EVT_SIZING event generated on a frame border click vs. the
wx.EVT_SIZING event generated from dragging the frame border, and they are
identical. So it seems to me there is no extra information here. Can anyone
clarify what wx.EVT_SIZING is for?
Also, if you have any other suggestion for catching the
end-of-resizing-operation event, I'd love to hear them.
Thanks,
Tim