I\'ve created a form that hosts one or more \'child\' forms. In my edit mode, each child form shows its border and caption bar allowing it to be moved and sized (a bit like
I think MDI is the easiest way, in the main form set FormStyle=fsMDIForm, in the childs FormStyle=fsMDIChild.
That's it, this way you dont have to set the parent to make it work.
Call Windows.SetFocus(Form.Handle)
which is somewhat more forceful than TForm.SetFocus
. Specifically Windows.SetFocus
will focus and activate a form that is inactive which I suspect is your main problem.
Having more than one form active feels wrong.
Finally, did you consider using MDI? It still works.
What's causing the behavior is the VCL's parenting mechanism. I don't know the exact reason, would take some time to figure it out I guess since it's somewhat a complicated mechanism.
You can get your desired behavior with parenting by the api:
procedure TForm1.Button1Click(Sender: TObject);
var
Frm : TForm;
begin
Frm := TForm3.Create( Self );
// Frm.Parent := Self;
windows.SetParent(Frm.Handle, Handle);
Frm.Visible := True;
You'll lose some synchronization with the VCL for sure, like parent dependent properties, anchoring, ownership etc.. It might even be problematic with respect to the api, like the missing WS_CHILD flag... Try it and see if it works to your needs..
To have a feel of more than one active form, you can tell any of them to paint accordingly:
SendMessage(Frm.Handle, WM_NCACTIVATE, WPARAM(True), 0);
When any form receives this message it will redraw its non-client area to reflect its (supposedly) activated status. Passing 'false' for wParam will cause the opposite.