WXMLC Version/Release info
v0.94 6/19/02
-added code to prevent multiple instances of the program from launching
v0.93 6/7/02
-now correctly converts < > & and " into XML (thanks Karissa!)
-now correctly converts comments in scripts (again thanks to Karissa)
-removed the silly "system info" button from the About dialog
v0.92 6/6/02
-fixed one last sneaky little bug in script selection
-included a reference in the readme to the eScape FAQ section on Java security
settings
v0.91 5/16/02
-variable conversion enabled
-now prevents selection of network folder ffor saving XML file (which caused a
crash)
-added hyperlinks to About box
-added link to web page in help menu
-fixed a a few bugs in script selection.
v0.90 5/13/02
-first release
v0.84 4/29/02
-now removes spaces from script names and replaces with underline character "_"
(see known issues below)
-readme.txt mostly rewritten
-enabled ability to convert game window default colors (hopefully more windows
to come)
-added setting to choose method of conversion for sounds string highlights
-now clears script conversion page if script file path settings are changed
-now reads user-configured sound and script path settings from the Wizard
-added ability to convert user-customized colors in the Wizard to eScape-compatible
palette
-revamped much of settings dialog choices, code, layout, and messaging
-made use eScape-compatible palette the default color setting
-string highlights output file overwrite check wasn't working; it is now
-squished a subtle bug in character selection and a few other tiny bugs
v0.83 3/7/02
-enabled eScape-compatible highlight color conversion of Wizard highlight
palette
-cleaned up highlight conversion logging a little
-enabled version upgrade recognition routine
v0.82 3/3/02
-cleaned up one teeny bug in script selection
v0.81 3/1/02
-First limited beta
Known Issues/Bug List
4/29/02
- Does not check for pre-existing file names when replacing spaces with
underlines in script file names. This may cause eScape to import two scripts
with identical names, which results in the first script getting overwritten by
the second script. A workaround is to rename your script files to make sure you don't have any scripts that can cause this kind of conflict.
- Macro conversion not enabled.
- Doesn't (yet) convert user-defined command-line character for Wizard script
execution.