>>>Dragan,
>>>
>>>It seems to me that (_beautify) requires two parameters.
>>>
>>>

>>>do (_beautify) with "file1", "file2"
>>>

>>>
>>>gave no error messages (at least, not every time!), but it didn't give any useful result either!
>>
>>I seem to remember that GenScrn took two parameters and the first one was supposed to be the currently open project, and if you supplied none, it created a dummy project on the fly and deleted it on exit. Too bad the beautifier source is not included here. FoxDoc source is there, and I wonder whether the beautifier is just a part of it - it would make sense.
>

---

>_Beautify receives 2 parameters from the dialog box that allows you to specify how Beautify.App should run. The 1st param is the name of the file containing the source code (typically something like 3elo003n.tmp - this is created by the VFP IDE). The 2nd param is a 36 byte string composed of 9 4 byte fields, it looks like only the first byte of each 4 bytes is used. This 2nd parameter contains details of the selection on the Beautify dialog box. I don't have the exact spec of the layout of this 2nd param but it should be easy enough to work out:
>
>Write a simple Beautify.app that accepts the two params, and for each of the permutations of the beautify dialog, display the ascii codes of each byte of the 2nd param.
>
>Just FYI: Beautify returns the name of a new .tmp file that contains the results of the beautification. The VFP IDE replaces the content of the current window with the contents of this new file, and then deletes it.

and if you just want to skip through the Beautify dialog, you can use something like:

KeyBoard "{Alt+T}f{enter}"
DoEvents