Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!elroy.jpl.nasa.gov!usc!trwind!venice!press
From: press@venice.SEDD.TRW.COM (Barry Press)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Scroll Bars in Child Windows
Message-ID: <1111@venice.SEDD.TRW.COM>
Date: 29 May 91 06:18:09 GMT
References: <1109@venice.SEDD.TRW.COM> <1991May28.193958.9492@hyper.hyper.com>
Reply-To: press@venice.sedd.trw.com (Barry Press)
Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA
Lines: 24

In article <1991May28.193958.9492@hyper.hyper.com> bonneau@hyper.UUCP (Paul Bonneau,,) writes:
>In article <1109@venice.SEDD.TRW.COM> press@venice.sedd.trw.com (Barry Press) writes:
>>I've setup a child window with a horizontal scroll bar, and am now trying to
>>make the scroll bar do something.  Unfortunately, what I get are not
>>WM_HSCROLL messages to the child window, but WM_SYSCOMMAND messages with
>>wParam set to SC_HSCROLL.  lParam appears to be the mouse coordinates.
> ... A lot of useful suggestions deleted ...

I want to thank everyone who replied, many of which I could not send back
to from my site for some net reason.

In any event, for those who may see that same effects, it turns out that
the WM_HSCROLL is apparently generated by Windows when it gets the
WM_SYSCOMMAND + SC_HSCROLL into the DefWindowProc.

What I had done was to intercept ALL WM_SYSCOMMAND messages in order to
prevent the window (which has a caption) from being moved, etc.  By
checking for this message and passing it along, the WM_HSCROLL's started to
show up.



-- 
Barry Press                                 Internet: press@venice.sedd.trw.com