Re: child window copies from parent "under" it
Dan
what do you envisage this "child" window doing? What behaviours are you
expecting? I ask this because in Windows, the concept of a window is very
broad. Every control, such as buttons, static text, combo box, etc... , is a
"window". Each of these are attached to a parent window and stuck in place
(unless you explicitly move them in your program). If what you are after is
a window with title bar, etc... that is somehow associated with a parent,
but also independent, maybe you are looking for something like a Multiple
Document Interface (MDI) window?
-----
cheers,
Derek Parnell
>Subject: Re: child window copies from parent "under" it
>
>
>Wolf,
>
>I tried (& probably originally also tried) just using "WS_CHILD", and the
>result was a *borderless* window, with no caption bar, which isn't really
>what I was hoping for; that's why I tried combining the frame and menu
>styles that I did.
>
> And nothing I saw at MS library site said I shouldn't; here's what it said
>about WS_CHILD: Creates a child window. A window with this style cannot
>have a menu bar. This style cannot be used with the WS_POPUP style."
>
>So now I have tried, not necessarily for any good reason, "WS_CLIPCHILDREN"
>for my parent window, but I get no sysmenu on it to close the main, AND no
>sysmenu on the child either, so I can't close either.
>
>I've gotta assume that *someone* has at one time or another for one reason
>or another created a "child" window that *works* and isn't strange??
>
>All I'm trying to do is to create an *example* of how to create a child
>window, to include with my "examples gateway" for Win32Lib, so if any one
>has a better, functional example, please send it to me.
>
>Dan
|
Not Categorized, Please Help
|
|
