🚀 go-pugleaf

In article <MUFFY.92Jul28115801@anableps.berkeley.edu> muffy@anableps.berkeley.edu (Muffy Barkocy) writes:
>
>I have an edit control in which I am trapping various WM_VSCROLL
>messages.  Under certain circumstances, when I get an SB_LINEDOWN, I add
>lines to the window, position it to my satisfaction, and then return,
>without calling the default scroll handler.  If those circumstances do
>not hold, I just call the default handler.
>
>So, what happens is that the little down arrow button at the bottom of
>the scrollbar gets "stuck" and keeps scrolling down until I click the
>mouse elsewhere.  It seems clear that there is something I need to tell
>this button that the normal procedure would tell it (something like
>"you're back up, don't send more scrolling messages until you're pressed
>again"), but I don't know what this is.  Can anyone help?


  If this is happening the the debugger then I would say it sounds 
  like exactly the same problem that I described here recently
  where TDW, and I'm told Codeview, gets multiple SB_LINEDOWN 
  messages because of some screwup with it's mouse handling.

---peter