🚀 go-pugleaf

  I'm a beginning Windows programmer using Borland C/C++ 3.1 
  and TDW (in dual screen mode) to learn about scroll bars and
  message handling.

  But when I'm using TDW, with a breakpoint set in my WndProc
  at my case for WM_VSCROLL, specif. in the SB_LINEDOWN code, I get 
  multiple (like 100's) of WM_VSCROLL messages with SB_LINEDOWN
  parameters for a single click of the mouse on the "down" button
  of the scroll bar!

  The program seems to behave normally if I'm not using TDW.

  On comp.os.ms-windows.programmer.misc someone suggested that
  it never gets the "release" of the mouse button because 
  control is immediately passed to TDW due to the breakpoint,
  so it thinks the mouse button is being held down.

  Someone else observed the same behavion with the Microsoft
  debugger.

  I called Borland's tech support and they said they had never heard
  of any problems like this.   So I called Borland's 900 tech support
  line and they said "of course" this problem exists!   I guess this means
  Borland will give you the wrong answer for free, but you have to pay
  $2 a minute to get the right answer!

  
  I also noted that my programs crash with an Exception 13 (addressing
  error  --  in TextOut, according to TDW) when I try to run them and
  Winsight at the same time.  Even Petzold's "Hello Windows" program
  screws up --  not crashing, but outputting garbage text instead of
  "hello windows" -- when Winsight is running, although it's well-behaved
  otherwise. 

  Comments or Winsight insight?

  Thanks in advance.


---peter