>>It's called "hacking", and wouldn't be necessary if one had an ASCII representation of the Class or Form.
>
>It isn't hacking, but there is NO WAY I want to define a form in code. Doing this visually is the only way to go.

>It isn't hacking, but there is NO WAY I want to define a form in code. Doing this visually is the only way to go.

As usual, you take things out of context (or cannot be bothered reading the previous posts).

I already stated previously I wanted "two-way programming"; ie.

- design the Form "visually"
- save it as "text"
- then have the !!! >>> option <<< !!! to add "code" using whatever editor one prefers ... going back to (only) the "visual tools" when it is necessary to tweek the GUI.

If you want to work with only the "Visual Tool" (and all the "method windows", blah, blah), you have that choice; but you also have the "text alternative".

There is a world outside of VFP where there is common practice (and it didn't require a VCX/SCX to accomplish).