home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!usc!elroy.jpl.nasa.gov!ames!agate!usenet.ins.cwru.edu!alpha.ces.cwru.edu!turnbull
- From: turnbull@ces.cwru.edu (John Turnbull)
- Subject: Re: Is it really this bad, or is it just me
- Message-ID: <1992Jul28.134522.11108@usenet.ins.cwru.edu>
- Sender: news@usenet.ins.cwru.edu
- Nntp-Posting-Host: ida.ces.cwru.edu
- Organization: Case Western Reserve University
- References: <1992Jul28.090409.1@cortex>
- Date: Tue, 28 Jul 92 13:45:22 GMT
- Lines: 19
-
- In article <1992Jul28.090409.1@cortex> mboucher@cortex.prospect.com (Mike Boucher) writes:
- >Hey there,
- >
- >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. It's
- >amazingly aggrivating, but, unlike Borland, (flame on) Microsoft doesn't even
- >have a phone number to call to find out obout S**T like this (flame off).
- >
- >It just might be in windows instead of the debugger.
- >
-
- 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.
-
- John
-
-