Re: Fighting (with win32lib?) for a reasonable UI design
- Posted by Lewis Townsend <keroltarr at hotmail.com> Jan 20, 2001
- 426 views
------=_NextPart_001_0000_01C082E6.7042F860 Hello George, In design #1 are you specifying the secondary windows as "children" of th= e primary. =20 >From my understanding, this could cause the problem of on-toppedness you = are =20 experiencing. I don't believe any window has to have a parent. I think th= e window you =20 open with WinMain() will be the "primary" window meaning that closing it = will close the app. The others don't have to be children of the primary to be closed whe= n it is. But I don't know a lot about win32lib (only used it a little) Hope this helps, Lewis Townsend Design #1 for two major functional areas: Place each in a separate window= , with a master window that offers menu options and perhaps other functionality common to the two areas (subwindows). To my dismay, I found that in doing this, the secondary (child) windows are "always on top" of the parent window. Not acceptable. Any of the 3 windows needs to be capable of on-topness, per the user's choice.<br clea= r=3Dall><hr>Get your FREE download of MSN Explorer at <a href=3D"http://e= ------=_NextPart_001_0000_01C082E6.7042F860 <HTML><BODY STYLE=3D"font:10pt verdana; border:none;"><DIV>Hello George,<= /DIV> <DIV> </DIV> <DIV> </DIV> <DIV>In design #1 are you speci= fying the secondary windows as "children" of the primary. <BR>From my und= erstanding, this could cause the problem of on-toppedness you are </DIV> = <DIV>experiencing. I don't believe any window has to have a parent. = I think the window you </DIV> <DIV>open with WinMain() will be the "prima= ry" window meaning that closing it will close the</DIV> <DIV>app. The oth= ers don't have to be children of the primary to be closed when it is.</DI= V> <DIV> </DIV> <DIV>But I don't know a lot about win32lib (only use= d it a little)</DIV> <DIV> </DIV> <DIV>Hope this helps,</DIV> <DIV>L= ewis Townsend<BR></DIV> <DIV><BR></DIV> <BLOCKQUOTE style=3D"BORDER-LEFT:= #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5p= x; PADDING-RIGHT: 0px"> <P>Design #1 for two major functional areas: Plac= e each in a separate window,<BR>with a master window that offers menu opt= ions and perhaps other<BR>functionality common to the two areas (subwindo= ws).<BR><BR>To my dismay, I found that in doing this, the secondary (chil= d) windows<BR>are "always on top" of the parent window. Not acceptable. A= ny of the 3<BR>windows needs to be capable of on-topness, per the user's = ur FREE download of MSN Explorer at <a href=3D"http://explorer.msn.com">h= ttp://explorer.msn.com</a><br></p></DIV> ------=_NextPart_001_0000_01C082E6.7042F860--