mrwad99
asked on
SetWindowPos confusion
Ah hello
I have obtained the following code for creating a sub dialog on a main dialog. Basically, I have a combo box on the main dialog that determines which child dialog to display on the main dialog. The child dialog is created and positioned to be within an area defined by a picture control on the main dialog. Have a look at this:
pNewDialog->Create( this );
CRect rc;
m_wndSubDialogArea.GetWind owRect(rc) ;
ScreenToClient(rc);
pNewDialog->SetWindowPos(& m_wndSubDi alogArea, rc.left, rc.top, rc.Width(), rc.Height(), SWP_NOACTIVATE | SWP_NOSENDCHANGING);
pNewDialog->ShowWindow(SW_ SHOW);
Assume that pNewDialog is a CDialog derived class, and m_wndSubDialogArea is the picture control where the sub dialog sits.
OK then. Having looked at this code, I am not sure on what the first parameter of SetWindowPos is doing exactly. I have read the docs, and it talks about Z order. Is this the Z order that is iterated through when we press Alt-Tab ?
Now then. I changed this parameter from my picture control to
&wndTopMost
and instead of the child dialog being fit nicely into my picture control, it appeared with its top left corner in the main dialog's top left corner.
?!?
I experimented with other values: wndBottom works fine, wndTop works but I can still see the outline of my picture control (black), and wndNoTopMost does the same as wndTopMost.
Can someone please explain these results ?
I need to understand this as I have a second question which can be answered when this first one has.
75pts/question
TIA
I have obtained the following code for creating a sub dialog on a main dialog. Basically, I have a combo box on the main dialog that determines which child dialog to display on the main dialog. The child dialog is created and positioned to be within an area defined by a picture control on the main dialog. Have a look at this:
pNewDialog->Create( this );
CRect rc;
m_wndSubDialogArea.GetWind
ScreenToClient(rc);
pNewDialog->SetWindowPos(&
pNewDialog->ShowWindow(SW_
Assume that pNewDialog is a CDialog derived class, and m_wndSubDialogArea is the picture control where the sub dialog sits.
OK then. Having looked at this code, I am not sure on what the first parameter of SetWindowPos is doing exactly. I have read the docs, and it talks about Z order. Is this the Z order that is iterated through when we press Alt-Tab ?
Now then. I changed this parameter from my picture control to
&wndTopMost
and instead of the child dialog being fit nicely into my picture control, it appeared with its top left corner in the main dialog's top left corner.
?!?
I experimented with other values: wndBottom works fine, wndTop works but I can still see the outline of my picture control (black), and wndNoTopMost does the same as wndTopMost.
Can someone please explain these results ?
I need to understand this as I have a second question which can be answered when this first one has.
75pts/question
TIA
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>>So why does SetWindowPos on its own not work ?
SetWindowPos() is used to set SIZE ,POSITION and Z-Order of a window...
if you use SWP_NOSIZE ...current size will keep unchanged...
if you use SWP_NOMOVE ...current positions will keep unchanged...
if you use both SWP_NOSIZE | SWP_NOMOVE position and size both will keep unchaged but then to work this you have to manually first set window size and positions..... after setting window to desired size and position you are calling SetWindowPos here just to change Z-Order because you have changed size and position with MoveWindow().. call to SetWindowPos with SWP_NOMOVE | SWP_NOSIZE will keep your size and positions intact but &CWnd::wndNoTopMost flag will set Z-Order.
2nd Q: When you create 2nd dialog runtime then z-order of windows changes.. and you need to manually set top and bottom window order manually.
-MAHESH
SetWindowPos() is used to set SIZE ,POSITION and Z-Order of a window...
if you use SWP_NOSIZE ...current size will keep unchanged...
if you use SWP_NOMOVE ...current positions will keep unchanged...
if you use both SWP_NOSIZE | SWP_NOMOVE position and size both will keep unchaged but then to work this you have to manually first set window size and positions..... after setting window to desired size and position you are calling SetWindowPos here just to change Z-Order because you have changed size and position with MoveWindow().. call to SetWindowPos with SWP_NOMOVE | SWP_NOSIZE will keep your size and positions intact but &CWnd::wndNoTopMost flag will set Z-Order.
2nd Q: When you create 2nd dialog runtime then z-order of windows changes.. and you need to manually set top and bottom window order manually.
-MAHESH
ASKER
Thanks.
IMHO contrary to the first comment from Mahesh the alt-Tab does work through the Z-order of the controls on the dialog, when you create/position a window on a dialog with other controls you can use the first parameter to control where the window is in the internal tab order.
ALT+TAB : well as per wordings yes.. But for explanations purpose I said Z-Order as top - bottom..one over another.. just to understand it better.
-MAHESH
-MAHESH
ASKER
>> the alt-Tab does work through the Z-order of the controls on the dialog
Thanks Andy.
When I press Alt-Tab I get a window with all the currently running apps displayed as icons. This dialog app I talked about in this question appears there, but the child dialog does not. I geuss if I created the child dialog as a separate dialog it would appear in the currently running apps list; or is that not what you meant ?
Thanks Andy.
When I press Alt-Tab I get a window with all the currently running apps displayed as icons. This dialog app I talked about in this question appears there, but the child dialog does not. I geuss if I created the child dialog as a separate dialog it would appear in the currently running apps list; or is that not what you meant ?
ALT+TAB : list appears main process NOT child dialogs.
-MAHESH
-MAHESH
My fault - I meant TAB not Alt-TAB to cycle through sibling controls which is based on their Z-ordering.
ASKER
I tried the code suggestion with using the SWP_NOMOVE flag and it still has the same effect. I then tried
pNewDialog->MoveWindow ( rc.left, rc.top, rc.Width(), rc.Height() );
pNewDialog->SetWindowPos(&
pNewDialog->ShowWindow(SW_
and it does work. So why does SetWindowPos on its own not work ?
Where I use m_wndSubDialogArea as the first parameter to SetWindowPos, I take it that means that the child dialog is one above the main dialog, i.e. it that is why it appears on top ?
My second question is related to showing and hiding the child dialogs. When I create a child dialog, and then I create another (when the user selects a different element in my combo box ) I don't destroy the first one, I simply hide it. Then, if I have not already created the new dialog to be displayed, I create it, otherwise I just show it (as I will have previously hidden it). I found that just hiding and showing the dialogs resulted in still seeing the hidden dialog behind the one that is currently visible. Say I hide a dialog that contains an edit control, then show one that contains a combo in the same place as the edit control. When I click the combo, I suddenly see the edit control and focus gets set to it, rendering my combo unusable. I then changed the Z order of the dialog that I hide to be &CWnd::wndBottom, and this fixed the issue.
Is this the best way of solving this, or can you see a better way ?
Thanks again.