Re: Quick Question!
From: Jeff Partch (jeffp_at_mvps.org)
Date: 05/14/04
- Next message: Frank Hickman: "Re: CAsyncSocket and receive"
- Previous message: James Ryan: "Re: list.remove() crash."
- In reply to: Joseph M. Newcomer: "Re: Quick Question!"
- Next in thread: Yasoo: "Re: Quick Question!"
- Reply: Yasoo: "Re: Quick Question!"
- Reply: Joseph M. Newcomer: "Re: Quick Question!"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 14 May 2004 12:07:34 -0500
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:pbr9a017n1djv2et75s6l4mdam7db2sht6@4ax.com...
> As I pointed out, I've seen a lot of problems with this approach. There
seems to be no
> compelling argument in its favor, and the number of problems I've seen is
fairly large.
Not sure how compelling it is, but a window should be expected to render
its background in response to WM_ERASEBKGND. If a dialog renders a custom
background, then it needs to conform to this reasonable expectation. I'd go
so far as to say that a window that does not do this is broken by design.
Once people start exploring dialogs with say bitmap backgrounds, they then
start exploring transparent controls -- the only reliable way I've found to
achieve this is to capture the dialog background into a memory bitmap passed
in a memory dc with a WM_ERASEBKGND to its parent, and then BitBlt your
portion in response to your own WM_ERASEBKGND.
-- Jeff Partch [VC++ MVP]
- Next message: Frank Hickman: "Re: CAsyncSocket and receive"
- Previous message: James Ryan: "Re: list.remove() crash."
- In reply to: Joseph M. Newcomer: "Re: Quick Question!"
- Next in thread: Yasoo: "Re: Quick Question!"
- Reply: Yasoo: "Re: Quick Question!"
- Reply: Joseph M. Newcomer: "Re: Quick Question!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|