home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!yoyo.aarnet.edu.au!sirius.ucs.adelaide.edu.au!sirius!jeremy
- From: jeremy@cs.adelaide.edu.au (Jeremy Webber)
- Newsgroups: comp.os.ms-windows.programmer.misc
- Subject: Re: Is it really this bad, or is it just me?
- Message-ID: <JEREMY.92Jul29090423@chook.adelaide.edu.au>
- Date: 28 Jul 92 23:34:23 GMT
- References: <Bs3Mpp.5ML@apollo.hp.com>
- Sender: news@ucs.adelaide.edu.au
- Organization: Digital Arts Film and Television
- Lines: 24
- Nntp-Posting-Host: chook.cs.adelaide.edu.au
- In-reply-to: nelson_p@apollo.hp.com's message of 28 Jul 92 12:29:49 GMT
-
- The short answer is: yes, its really this bad.
-
- I had a similar experience debugging code with scrollbars (TScroller) under TPW
- (Windows 3.1). I had trace write code within the module to write to the
- "wincrt" window, a sort of text i/o window accessible by the standard Pascal
- readln and writeln statements.
-
- Sometimes (only sometimes) when these trace writes occurred, the scrollers
- would see a mouse down event, but not the corresponding mouse up event, causing
- them to keep hold of the mouse capture, breaking the application. I suspect
- that it was caused by accessing another task while the mouse capture was set
- to the scrollers (wincrt starts its own control task).
-
- You are probably seeing a similar interaction between BC++ and TDW.
-
- Good luck!
- Jeremy
-
- --
- --
- Jeremy Webber Internet: jeremy@cs.adelaide.edu.au
- Digital Arts Film and Television, jeremy@chook.ua.oz.au
- 3 Milner St, Hindmarsh, SA 5007, Phone: +61 8 346 4532
- Australia FAX: +61 8 346 4537
-