It appear that in version 8 - I guess - MS changed the behavior so that an initial click on VFP activates it but does not pass the click to whatever form, report, etc. is active. The thing about stray mouse clicks is that if you accidentally click outside of the active app and another app is under it, then you could click some button that has serious consequences. Imagine if that button were "Launch the missiles". Oh, man, what have you done then!! <g> So some apps always took an initial click on the app when the app was not active as a "activate the app" click and did not pass it to whatever control you - by chance - happened to click on. This - I think - is now how VFP operates and it may carry over to VFP system windows, also. I'd have to test it. I've become so accustomed to the changes now, it's hard to remember. Since VFP there have been subtle interface changes that make the IDE harder to get around in, but the VFP team doesn't seem to recognize this. Anyway, I've noticed what you're talking about.

And then there's the problem that I've seen ever since VFP 6 and maybe before where you click the Close button of a window and it does not close the window. But if you move the mouse on and off the Close button - without clicking - the button will depress and undepress. You have to click a second time to close the window. I'm not sure why they can't fix this irritating problem.


>Hi
>
>Since version 8.0 of VFP I have experienced the annoying habit of having to often double click a window control in both Design mode and runtime before the mouse activates the form or control. Sometimes one click is enough but often it requires two mouse clicks.
>
>Therefore I find myself clicking on a form and begining to type only to realize that the form is not active and nothing I typed was recorded. I then re-click on the item an begin again. This also happened when I was changing a table structure the other day. I changed a field type and then clicked on the next field type drop down box to change another field but it did not receive focus so then I had to re-click it again. This is especially true for listboxes where I may have to click twice before a particular element gets focus.
>
>This never happened before Version 8.0 but it is an annoying feature/bug now.
>
>Does anyone else experience the same phenomenon? Does anyone know what was changed and whether this is a design feature. This happens on different workstations so it is not specific to my workstation.
>
>Thanks
>Simon White