Early BETA Dialog code generator

[hutch--]

I have got the bare application up and going. It is designed to work with Ketil Olsen's ResEd.exe resource editor which you will need to obtain, version 2205b or later as the earlier version did not support calling it from another directory.

Currently the tool supports setting up your own preferred versions of ML, LINK, RC and CVTRES from later sources like a DDK or SDK. It directly supports Pelle's POLINK and PORC and the tools you choose are written into the "makeit.bat" file that is used to build the application. It has been tested using the Microsoft binaries from the current DDK and it has been tested using the Pelle's linker and resource compiler in their own locations in the Pelle's C install and it is working correctly with both.

The tool writes an XML file to disk which is written into the RC file before it is passed to ResEd.exe so that the application has the later common control interface support.

The code design is so far very basic, It writes directives to support both MMX and the later XMM (SSE) which you can comment out if you must support legacy hardware. It writes a working "WndProc" that has WM_COMMAND processing for "Button" class controls and it has a following procedure that is for normal GDI code called from WM_PAINT.

The tool currently comes with its own INI file that stores the tools paths, later version will be able to create the file from scratch if it is not present. Later versions will also have a settings file that will retain the user settings on the main window, at the moment there is only the choice of linker and resource compiler and this must be set manually.

When you set up ResEd.exe you must ensure that the equates are contained in the RC file, not in a remote file as the RC file parser does not search for external files. It is a one pass parser that loads the equates into a hash table then matches the equates to each control on the dialog once the RC file has been created. It then writes the format that the tool requires into the list box for the next operation which is code generation from the data stored in the list box.

Future list.
Write subclass procedures for at least some of the cotrols, list boxes and combo boxes will probably be the first.
Once the range of settigs is understood, write a settings file that is maintained by the tool.
Put something useful in the About Box.  :bg

Any constructive comments will be appreciated.