Hi Tod,

I think this is a very good behaviour ( Start at VFP7 )
( a fix for a problematic use of WAIT WINDOW on VFP6 )
GGGGRRRRR!!!!!!! BUT FOR Modeless Childs the VFP6 behaviour still
then i think it is a casual changing or a single customer patch request to VFPT.
No good.

For ShowWindow = 0, the VFP6 behaviour still,
and i think it is good for backward compatibility
on simple single frame application.

On VFP6, WAIT WINDOW is not usefull with desktop forms ( free dialogs ).

Run this, where the child is a dialog on DeskTop;

PUBLIC oform1, oform2

oform1=NEWOBJECT("form1")

oform1.Show
RETURN

DEFINE CLASS form1 AS form

	ShowWindow = 2	&& As top-level form
	WindowType = 0	&& Modeless

	AutoCenter = .T.
	Caption = "Form1"
	Name = "Form1"
	height = 480
	width = 640

	PROCEDURE Click
		WAIT WINDOW ;
			"Form1: ShowWindow = " + ;
			ALLTRIM(STR(this.ShowWindow)) + ;
			" WindowType = " + ;
			ALLTRIM(STR(this.WindowType)) TIMEOUT 3

		oform2=NEWOBJECT("Dialog")
		oform2.Show
		THISFORM.Release()
	ENDPROC

ENDDEFINE

DEFINE CLASS Dialog AS form

	ShowWindow = 1	&& In top-level form
	WindowType = 1	&& Modal
	Desktop	   = .t.	&& <========= !!!!!!!!!!!!!!
	
	AutoCenter = .T.
	Caption = "Form2"
	Name = "Form2"
	height = 480*.5
	width = 600*.5

	PROCEDURE Click
		WAIT WINDOW ;
			"Form2: ShowWindow = " + ;
			ALLTRIM(STR(this.ShowWindow)) + ;
			" WindowType = " + ;
			ALLTRIM(STR(this.WindowType)) TIMEOUT 3

		THISFORM.Release()
	ENDPROC

ENDDEFINE

Result:
when a form have :
ShowWindow = 2
or
ShowWindow = 1 && In top-level form
WindowType = 1 && Modal

the WAIT WINDOW is put within the form,
otherwise it is put within the Top frame form.
Fabio