>I use Foxtools a lot, in fact it's always loaded by my appliations, since it provides a lot of functionality in dealing with files, paths and drives. Since it is, and a very direct way of retrieving the window handle exists, I prefer to use it when I can.
>
>From what I've understood from the threads from last year's DevCon, some of the functions from Foxtools are going to become part of the language. If you're interested, there's a fully cross-referenced help file available in the download section (Coding, Syntax & Commands).
>
>Quick question. FindWindowEx() requires the class name of the window be passed. The documentation, however, doesn't mention whether or not in can be NULL, so I assume that it can't be. Now getting the class name of the main VFP window isn't a problem. However, I've noted (using Spy++) that not all the class names of the windows match the parent. Admittedly, I haven't researched this very carefully. So the questions are: Can the class name be NULL, and if not, are all the form's class names the same as the parent?
>
>TIA,

FindWindow requires a class name as it's first parameter as well. I declare it an integer and pass 0. Just musing, I wouldn't think that all of the class names would necessarily be the same as the parent.

Thanks for the info on Foxtools. I have used it years ago with FPD/W because it was almost necessary. <g>

I think that it would be cool if VFP decided to support the lib extentions. It would also be nice if the API functions were implemented a bit further. Despite all of the research that I have done, classes I've looked at, I still have trouble with structs and VFP. I just gave up.

Donald