"Karl E. Peterson" wrote:

> Dan wrote:
> > I'm working in VB6 and would like to set the background of the
> > VScrollbar control to gray (it defaults to white).  There is
> > backcolor property for this control; is there any way to do what I
> > want.
>
> Unfortunately, that's a bug in (all versions of) 32-bit VB.  See the 2nd
> Question in this article:
>
>   http://vb.mvps.org/articles/ap199810.pdf
>
> Short story is, you need to subclass the form, and "eat" the
> WM_CTLCOLORSCROLLBAR messages it gets.
> --
> Working without a .NET?
> http://classicvb.org/
>
>
>

> "Karl E. Peterson" wrote:
>
>> Dan wrote:
>>> I'm working in VB6 and would like to set the background of the
>>> VScrollbar control to gray (it defaults to white).  There is
>>> backcolor property for this control; is there any way to do what I
>>> want.
>>
>> Unfortunately, that's a bug in (all versions of) 32-bit VB.  See the
>> 2nd Question in this article:
>>
>>   http://vb.mvps.org/articles/ap199810.pdf
>>
>> Short story is, you need to subclass the form, and "eat" the
>> WM_CTLCOLORSCROLLBAR messages it gets.
>> --
>> Working without a .NET?
>> http://classicvb.org/

"Karl E. Peterson" wrote:

> Dan wrote:
> > By "eat", do you mean that I return a brush handle to paint the
> > background gray, or do you mean that I should simply return 0?
>
> As I wrote in that column:
>
>   "By simply instructing MsgHook to intercept this message, but not reacting
> in any fashion whatsoever to the receipt of the message, you instruct
> Windows to use the default colors for these controls."
>
> So, yeah, returning zero would be the proper non-response. <g>
> --
> Working without a .NET?
> http://classicvb.org/
>
>
>
> > "Karl E. Peterson" wrote:
> >
> >> Dan wrote:
> >>> I'm working in VB6 and would like to set the background of the
> >>> VScrollbar control to gray (it defaults to white).  There is
> >>> backcolor property for this control; is there any way to do what I
> >>> want.
> >>
> >> Unfortunately, that's a bug in (all versions of) 32-bit VB.  See the
> >> 2nd Question in this article:
> >>
> >>   http://vb.mvps.org/articles/ap199810.pdf
> >>
> >> Short story is, you need to subclass the form, and "eat" the
> >> WM_CTLCOLORSCROLLBAR messages it gets.
> >> --
> >> Working without a .NET?
> >> http://classicvb.org/
>
>
>
>

"Karl E. Peterson" wrote:

> Dan wrote:
> > Thanks Karl.  I downloaded MsgHook, and applied the code from your
> > article,
>
> Remember, MsgHook is but a convenience, especially since VB5 added AddressOf
> to the arsenal.  To see my method of native subclassing, check out:
>
>   http://vb.mvps.org/samples/HookMe
>
> > but I'm still getting the same behavior.  I wonder if it's
> > because the vscrollbar is part of Francesco Balena's Superlistbox
> > control:
> >
> http://www.fawcette.com/archives/premier/mgznarch/VBPJ/1999/08aug99/fb0899.pdf
>
> Ah, well, as Ken says, all bets are off in that case.  I have no idea what
> Francesco did, without a lot of dissection.  The reason I was hooking the
> form in the first place, was Windows sends that message to the scrollbar's
> parent window.  You familiar with Spy++?
> --
> Working without a .NET?
> http://classicvb.org/
>
>
>

"Karl E. Peterson" wrote:

> Dan wrote:
> > Yes, I'm very familiar with Spy++ (not sure whether to brag about it
> > though :).
>
> <g>
>
> > I think Ken is right: there is no hWnd property on Balena's scrollbar
> > (even though it's named vScrollBar).
>
> Ouch.  Well, time to reinvent the wheel, then, eh?  Bummer...
>
> Hmmmm, why don't you just wave the Spy++ window finder cursor over it, just
> to be sure.
> --
> Working without a .NET?
> http://classicvb.org/
>
>
>