Re: owner/owned zorder
[email protected] Thu, 29 May 2003 10:27:20 -0700
| Newsgroups | gmane.comp.windows.shell-shocked.devel |
|---|---|
| Message-ID | <[email protected]> |
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? > - 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) -rabidcow ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today! __________________________________________________ Subscription options and archive: http://www.freelists.org/list/shell-coding