Re: owner/owned zorder

"xnowfall" <[email protected]> Thu, 29 May 2003 20:14:13 +0200
Newsgroups gmane.comp.windows.shell-shocked.devel
Message-ID <00c001c3260e$1cefa190$32b4a8c0@xnowmachine>
>
> On Thu, 29 May 2003 16:42:07 +0200 "xnowfall" <[email protected]>
> writes:
> > litestep's main window isn't owned or parented to anything,
> > but modules like desktop2, label and layercuts are owned by
> > it.
>
> Is there any reason to do that?
>
> If having the windows owned by the litestep window causes the problem,
> why not just avoid setting the owner?
>

don't know if that's why it was originally added, but unowned topmost
windows with a caption show up in the taskmanager


> >  - the litestep window should possibly use something like
> > (((WINDOWPOS *)lParam)->flags |= SWP_NOSIZE | SWP_NOMOVE
> > | SWP_NOZORDER | SWP_NOOWNERZORDER) for WM_WINDOWPOSCHANGING.
> > this to let it protect the zorder itself in case some modules
> > don't follow the rules above
>
> The litestep window should probably be created with HWND_MESSAGE, which
> would avoid zorder all together (on systems where it's supported)
>

it couldn't then be the owner of labels/layercuts etc without them becomming
message windows too though, right?


__________________________________________________
Subscription options and archive:
http://www.freelists.org/list/shell-coding