From: Nikolay Sivov <bunglehead@gmail.com>
Subject: Re: [PATCH 1/4] comctl32/combo: Add test for WM_CTLCOLORSTATIC
Message-Id: <CAG4Z_JJZhBD95nhY67E5h+VA4SAP71a4sgT3GBKyex986PVg1w@mail.gmail.com>
Date: Mon, 23 Sep 2019 08:10:50 +0300
In-Reply-To: <2797100.vt2BND2DkA@arch>
References: <20190922141158.59325-1-dark.shadow4@web.de> <CAG4Z_JJU+Ew-338-BJD=sJ1HjwyzAmB+49GzoojwhNAr0ckumA@mail.gmail.com> <2797100.vt2BND2DkA@arch>

On Sun, Sep 22, 2019 at 7:41 PM Fabian Maurer <dark.shadow4@web.de> wrote:

> > What should happen if parent/owner does not handle WM_CTLCOLOR* message?
>
> Then it should get passed to DefWindowProc. It's currently handled by
> DefWindowProc as well, but with these patches the parent is given a chance
> to
> handle it itself before it's passed to the default handler.
>

I don't see this happening with your patch.


>
> Regards,
> Fabian Maurer
>
>
>

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Sep 22, 2019 at 7:41 PM Fabian Maurer &lt;<a href="mailto:dark.shadow4@web.de">dark.shadow4@web.de</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">&gt; What should happen if parent/owner does not handle WM_CTLCOLOR* message?<br>
<br>
Then it should get passed to DefWindowProc. It&#39;s currently handled by<br>
DefWindowProc as well, but with these patches the parent is given a chance to<br>
handle it itself before it&#39;s passed to the default handler.<br></blockquote><div><br></div><div>I don&#39;t see this happening with your patch.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Regards,<br>
Fabian Maurer<br>
<br>
<br>
</blockquote></div></div>