Looking at Kensuke's code, he uses an internal queue to store messages that need to be processed by child windows. For some reason this queue is not being properly reset when the messages are processed. Or, it could be as simple as returning the wrong value after processing these messages, causing Windows to send them again.
Harold -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jean-Claude Gervais Sent: Thursday, December 12, 2002 1:52 PM To: [EMAIL PROTECTED] Subject: RE: Rootless mode This may be obvious, but the difference between the two is that Windows sends you a bunch of messages when you're dragging the window when fulldrag is in effect... So it might be some message handler repositioning the window during one of those notifications... Maybe a WM_SIZE or WM_WINDOWPOSCHANGING... Anyhow, I think running spy and just looking in on the stream of messages that a window doing fulldrag receives could be a way to figure out which message. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Harold L Hunt Sent: Thursday, December 12, 2002 1:33 PM To: [EMAIL PROTECTED] Subject: Re: Rootless mode Kensuke, Hmm... that sounds about right. Windows 2000 and Windows XP have that option on by default, I believe. Are you going to try to debug this? Harold Matsuzaki Kensuke <[EMAIL PROTECTED]> said: > Harold, > > I could not reproduce that bug, but now I found that this bug occur when > "Show window contents while dragging" enabled. > > Maximizing a window never stop too. > > Matsuzaki Kensuke > >
