home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!microsoft!hexnut!gregde
- From: gregde@microsoft.com (Greg Demichillie)
- Subject: Re: Is it really this bad, or is it just me
- Message-ID: <1992Jul29.155112.7877@microsoft.com>
- Date: 29 Jul 92 15:51:12 GMT
- Organization: Microsoft Corporation
- References: <1992Jul28.090409.1@cortex> <1992Jul28.134522.11108@usenet.ins.cwru.edu>
- Lines: 28
-
- In article <1992Jul28.134522.11108@usenet.ins.cwru.edu> turnbull@ces.cwru.edu (John Turnbull) writes:
- >In article <1992Jul28.090409.1@cortex> mboucher@cortex.prospect.com (Mike Boucher) writes:
- >>
- >>I've been having some screwy scroll bar problems as well, and Microsoft's
- >>Codeview does the same thing with multiple messages from one click.
- >
- > I think you'll find the problem is that windows never gets a mouse
- >up event, so it thinks you're holding down the mouse on the scroll down. I.e.
- >pressing the mouse button generates the linedown, and you then break, so
- >windows never see you releasing the mouse button.
- >
-
- This is exactly what happens. The context switch into the debugger happens
- after the mouse down and so the mouse up event is given to the debugger.
-
- This happens with every Windows debugger I've seen (including Codeview,
- TDW and Multiscope.) The only work around I'm aware is to use
- OutputDebugString to print lots of messages in your mouse tracking
- code. Using debuggers to step through mouse handling code just isn't
- my idea of fun.
-
- DISCLAIMER: I don't work on Codeview, but I've used it and other
- debuggers quite a bit.
-
- -Greg
-
- --
- Greg DeMichillie
- gregde@microsoft.com -- All opinions are mine, not Microsoft's --
-