fixes Alignment and Anchor calculation even before we have a window handle

Updated the following methods by rather checking the ComponentState,
than the HasHandle result. Why? Because we want alignment and anchor
calculations to work, even before we have a window handle. Something
that happens often when using a Frame-type design for the UI.

* HandleMove()
* HandleResize()
* UpdateWindowPosition()

Due to removing the HasHandle check in UpdateWindowPosition, we had
to do the HasHandle check in each backend code instead. We don't want
to trigger API calls when we don't have a window handle yet.

1 files changed, 11 insertions, 8 deletions

diff --git a/src/corelib/gdi/fpg_gdi.pas b/src/corelib/gdi/fpg_gdi.pas
index 6d1ff0c7..9eb9f952 100644
--- a/src/corelib/gdi/fpg_gdi.pas
+++ b/src/corelib/gdi/fpg_gdi.pas
@@ -1976,14 +1976,17 @@ procedure TfpgGDIWindow.DoUpdateWindowPosition;
 var
   bx, by: integer;
 begin
-  FSkipResizeMessage := True;
-  GetWindowBorderDimensions(Self, bx, by);
-  Windows.SetWindowPos(
-    WinHandle, HWND_TOP,
-    FLeft, FTop, FWidth + bx, FHeight + by,
-    SWP_NOZORDER);// or SWP_NOREDRAW);
-  Windows.InvalidateRect(WinHandle, nil, True);
-  FSkipResizeMessage := False;
+  if HasHandle then
+  begin
+    FSkipResizeMessage := True;
+    GetWindowBorderDimensions(Self, bx, by);
+    Windows.SetWindowPos(
+      WinHandle, HWND_TOP,
+      FLeft, FTop, FWidth + bx, FHeight + by,
+      SWP_NOZORDER);// or SWP_NOREDRAW);
+    Windows.InvalidateRect(WinHandle, nil, True);
+    FSkipResizeMessage := False;
+  end;
 end;
 
 { TfpgGDICanvas }