From e91d0dbf05ce8ba941053fbe66b07dd4c632d72e Mon Sep 17 00:00:00 2001 From: a1tsal Date: Fri, 27 Feb 2004 10:29:57 +0000 Subject: [PATCH] Minor additions, fixes, and clarifications. --- Build procedure.txt | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/Build procedure.txt b/Build procedure.txt index ebc4850..056b886 100644 --- a/Build procedure.txt +++ b/Build procedure.txt @@ -2,7 +2,7 @@ This explains how to make a new version of WylieWord. -The program source file is called "WylieWord developement copy.dot". +The program source file is called "WylieWord development copy.dot". This is what you edit with the VBA editor. When you have finished modifying it: @@ -13,22 +13,21 @@ I use "!!!" in comments to note known bugs that should be dealt with. Search for "!!!" and make sure anything left in that state is acceptable in the release. +Do "Debug > Compile" in the F11 window. Verify there are no +compilation errors. + Re-test everything that has changed since the last release, and -anything that might be affected by those changes. Do the testing with -the template loaded from the Word Startup folder. For some reason, -Word runs VBA differently when loaded from there; specifically, missing -type declarations are more likely to result in run-time errors. +anything that might be affected by those changes. Increment the version number in AboutWylieWord. Run PrepareDistribution in immediate window. - This runs automated tests. Verify that the results are OK. + This runs automated tests. The third set of tests may take ten minutes or so. + Verify that the results are OK. It also unbinds all the WylieWord keys. - This is critical to having WylieWord work correctly on - non-English keyboards. - After making the distribution, you will want to restore - the keybindings in the develoment copy by calling - WylieWordBindKeys. + This is critical to having WylieWord work correctly on non-English keyboards. + (After making the distribution, you will want to restore the keybindings + in the development copy by calling WylieWordBindKeys.) Save "WylieWord development copy.dot" @@ -48,4 +47,6 @@ In SEAU: Run the SEAU builder. Run the resulting self-extracting .exe file. -Re-test everything. \ No newline at end of file +Re-test everything. Do the testing with the template installed in and +loaded from the Word Startup folder. (Due to Word idiocy, VBA runs +differently (and usually worse) when loaded from there.) \ No newline at end of file