Dmitry Timoshkov dmitry@baikal.ru writes:
@@ -1070,9 +1072,10 @@ STATUSBAR_WMSize (STATUSWINDOWINFO *info width = parent_rect.right - parent_rect.left; x = parent_rect.left; y = parent_rect.bottom - infoPtr->height;
- MoveWindow (infoPtr->Self, parent_rect.left,
parent_rect.bottom - infoPtr->height,
width, infoPtr->height, TRUE);
- SetWindowPos(infoPtr->Self, HWND_TOP,
parent_rect.left, parent_rect.bottom - infoPtr->height,
width, infoPtr->height, SWP_NOZORDER);
What is this change for?
"Alexandre Julliard" julliard@winehq.org wrote:
@@ -1070,9 +1072,10 @@ STATUSBAR_WMSize (STATUSWINDOWINFO *info width = parent_rect.right - parent_rect.left; x = parent_rect.left; y = parent_rect.bottom - infoPtr->height;
- MoveWindow (infoPtr->Self, parent_rect.left,
- parent_rect.bottom - infoPtr->height,
- width, infoPtr->height, TRUE);
- SetWindowPos(infoPtr->Self, HWND_TOP,
parent_rect.left, parent_rect.bottom - infoPtr->height,
width, infoPtr->height, SWP_NOZORDER);
What is this change for?
HWND_TOP of course should be replaced by 0 since SWP_NOZORDER is specified. The change is aimed to be a simple optimization. If you don't like this part, just ignore it.
"Dmitry Timoshkov" dmitry@baikal.ru writes:
HWND_TOP of course should be replaced by 0 since SWP_NOZORDER is specified. The change is aimed to be a simple optimization.
Then you'd need to add SWP_NOACTIVATE for it to be identical to the previous code; but I don't think this kind of micro-optimization is useful, if all we want is to move the window it's clearer to use MoveWindow IMO.