Installation packages for a second ooDialog 4.2.2 beta are now available on SourceForge at:
The second beta only has a few changes from the first package. A small bug in the .DlgAreaU class has been fixed and the User Guide document has had a number of typos corrected. Otherwise the second beta package is the same as the first package.
ooDialog 4.2.2 is an enhancement release, with a large number of new features. The Release Notes and the ReadMe file that displays on the SourceForge download page contain a list of the bug fixes, enhancements, and other changes in 4.2.2.
Users of ooDialog should test the beta and report bugs or other problems through the ooRexx SourceForge tracker for bugs:
Beginning with the release of ooDialog 4.2.0, the installation of ooDialog has been decoupled from the interpreter. ooDialog 4.2.2 installs over the top of any ooRexx installation. It replaces the version of ooDialog in the ooRexx installation with ooDialog 4.2.2.
This type of ooDialog installation is called an "independent" ooDialog installation to indicate the ooDialog installation is independent of an ooRexx installation and, to a degree, the version of ooRexx installed.
ooDialog 4.2.2 requires a minimum ooRexx version of 4.1.0 to be installed on the target computer.
Installation is simple, done through a typical Windows installer. Pick the installation package that matches the bitness of the ooRexx installation. I.e., a 32-bit package for a 32-bit ooRexx and a 64-bit package for a 64-bit ooRexx. Note that the bitness of the operating system is not relevant here. If you have installed a 32-bit ooRexx on a Windows 64-bit system, you must install a 32-bit ooDialog.
The installer will detect the installed ooRexx, location, and version. If the ooRexx version is less than 4.1.0, or if there is no installed ooRexx, the installer will abort with a message explaining the
problem. Otherwise the installer will replace the current ooDialog with ooDialog 4.2.2.
Mark Miesfeld for the ooRexx Development Team