>Hi Herman,
>
>It's interesting that you've delved so deeply into this, and still the general case seems to be too difficult to handle with generic code. That strengthens the argument for making the compromise of adding some intelligence about the specific application that one is launching. For example you can easily get past a misleading splash screen if you know the window class name that you're waiting for in launching that particular application.
>
>Mike

Hi Mike,
Thanks for the comment :)

Yes, I'm agree with you. Eventhough maybe we can solve most of the problem with generic code, But it's just going to be more dirty and dirtier. At some point maybe we could crash the apps or even the system, I'm not sure about it. So looking from the situation, I prefer to code in a clean way.

If you check for the class name it will get confuse because many apps had the same class. For example VFP7, from the first time we launch VFP, it already has more than 2 hwnd with the same class (VFP77400000). Which one is the right one. I mean besides the parent. And also like you said it only works *if* we know what is the class name.
Actually, if it is only the splash screen we could pass this. Just check for the application name (exe) using the hwnd. But it also works only *if* it is only one apps at one time. Well..I'm not sure :)

Regards