Steve,

Try to bind to the VFP outer window _VFP.HWnd instead of inner _Screen.HWnd

	BINDEVENT(_VFP.HWnd, WM_EXITSIZEMOVE, ;
		ThisForm, "OnWindowResizeExit", ;
		BE_FireAfterEvent)

>
>I'm sorry. Someone came into my office and I sent the post mistakenly thinking that I had finished it. My ADD and 50+ yeast are conspiring against me I'm afraid...
>
>The problem with the code is that while the form WM_EXITSIZEMOVE can be trapped, If you maximize the form inside the VFP _Screen window and then resize the VFP _screen window you cannot trap the VFP _Screen's WM_EXITSIZEMOVE event using the same technique used to trap the event in the form. I am assuming that the message gets passed but that for some reason VFP eats it.
>
>This is important because I have a map on the form and I cannot afford to redraw the map from the Resize because it takes several seconds to do the redraw. I could use the workaround I used before finding about the WM_EXITSIZEMOVE event. I used a timer and constantly reset it to 500 from within the ReSize event. If the user stopped moving for half a second the map would redraw. Users did not like this because it introduced a noticable delay in redrawing the map. If I can coax this into working it will be the best solution.
>
>What do you think? Is the WM_EXITSIZEMOVE event there? If so, how can I get to it? Is there another workaround that I haven't thought of?
>