Looking for the latest version? Download ooRexx-4.1.0-all.zip (15.2 MB)
Home / ooDialog / 4.2.4 (preview)
Name Modified Size Downloads / Week Status
Parent folder
Totals: 4 Items   34.0 MB 4
ooDialog- 2014-02-17 11.3 MB 11 weekly downloads
ooDialog- 2014-02-17 11.4 MB 11 weekly downloads
ReadMe.txt 2014-02-17 9.7 kB 11 weekly downloads
oodialog- 2014-01-19 11.2 MB 11 weekly downloads
Release Notes ooDialog 4.2.4 ============================ The ooDialog 4.2.4 release is an enhancement and bug fix release. ooDialog 4.2.4 can be installed to any ooRexx installation, 4.1.0 or later. Beginning with the release of ooDialog 4.2.0, the installation of ooDialog has been decoupled from the interpreter. ooDialog 4.2.4 installs over the top of any ooRexx installation. It replaces the version of ooDialog in the ooRexx installation with ooDialog 4.2.4. 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.4 requires a minimum ooRexx version of 4.1.0. Installation ======================================================================== 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. 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.3. Note that the actions of the installer are dependent on the version of ooRexx, not the version of the installed ooDialog. For instance, if the installed ooDialog is version 4.3.0, but for some reason the user is not happy with that version, running the ooDialog 4.2.4 installer will replace the 4.3.0 version with the 4.2.4 version. At the time of the installation, *all* ooDialog programs must be halted and the ooDialog PDFs must be closed if they happen to be opened. Changes in ooDialog 4.2.4 since the release of ooDialog 4.2.3 ======================================================================== Bug Fixes in ooDialog: ---------------------- * Documentation Bug Fixes in ooDialog: ------------------------------------ * #209 ooDialog - calcDisplayRect() misnamed in doc Feature Requests in ooDialog: ----------------------------- * #580 Send proper args to the DRAW event handler. * #579 Send Rexx dialog control object to event handling methods. * #577 Get an icon image from an image list * #575 Send the Rexx Tab object to tab control event handlers * #574 Event connections should all have a 'willReply' argument * #573 ResouceImage class, the new() method should only need 1 argument * #572 ListView getImageList() /? setImageList should accept string keyword for image list type * #570 The system metric class should have values for the small and normal icons * #553 Add the StatusBar control to ooDialog * #581 Add item data capability to combo box * #588 There is no way to get a system brush in ooDialog * #589 There is no way to fill a rectangle without getting an outline around it * #590 Enhance the fillDrawing() method to accept a COLORREF Miscellaneous Fixes: -------------------- * New Functionality in ooDialog: ------------------------------ The stand alone installer has been enhanced to use a better check for locked files and to give the user a chance to close the open files and continue with the installation. New dialog classes: ------------------- ? New dialog control classes: --------------------------- ReBar control class: Rebar controls act as containers for child windows. StatusBar control class: Status bar controls provide a place for the application to display status information along the bottom of the dialog. ToolBar control class: A toolbar is a control window that contains one or more buttons. Each button, when clicked by a user, sends a command event notification to the dialog window that owns the toolbar. New utility classes: -------------------- ReBarBandInfo: The ReBarBandInfo class is a helper class for the ReBar dialog control class and represents information about a specific band in the ReBar. New Public Routines: -------------------- ? New Methods: ------------ In the DlgUtil class: --------------------- signed32() usigned32() In the ImageList class: ----------------------- getIcon() In the WindowExtensions class: ------------------------------ fillRect() getSysBrush() New Attributes: --------------- In the SM class: ---------------- * cxIcon * cyIcon * cySize * cySmIcon Enhanced Methods: ================= In the Button class: ------------------- * getImageList() and setImageList() methods accept string keywords for the alignment argument. In the EventNotification class: ------------------------------- * All event connection methods have an optional will reply type argument. This argument is added to those methods that did not have it. All of the will reply type arguments now accepted 3 values instead of 2. .true, .false, or the keyword 'SYNC'. See the documentation for the proper usage and what the values mean. addUserMsg() * an eighth optional argument is added that allows the programmer to specifiy how the interprter should expect the event handler to respond. I.e., do not wait, will reply wait, and sync wait. connectButtonEvent() * the DROPDOWN event is added. connectTabEvent() * The event handler for all events is now sent a third argument, the Rexx Tab object that is sending the event notification. In the Image class: ------------------- * The getImage() method has been enhanced to accept string keywords for the type and flags arguments. * The fromIDs() method has been enhanced to accept string key words for the typed and flags arguments. * The userIcon() method has been enhanced to accept string key words for the flags arguments. In the ImageList class: ----------------------- * The create() method has been enhanced to accept string key words for the flags argument. In the ListView class: ---------------------- * The getImageList() method has been enhanced to accept a string key word for the type agrument. * The setImageList() method has been enhanced to accept a string key word for the type agrument. In the ResourceImage class: --------------------------- * The new() method has been enhanced to only need 1 argument. The optional 2nd argument is no longer needed. * The getImage() method has been enhanced to accept string key words for the type and flags arguments. * The getImages() method has been enhanced to accept string key words for the type and flags arguments. In the TreeView class: ---------------------- * The getImageList() method has been enhanced to accept a string key word for the type agrument. * The setImageList() method has been enhanced to accept a string key word for the type agrument. In the WindowExtensions class: ------------------------------ * The fillDrawing() method has been enhanced to accept a COLORREF for the argument that specifies the bounding color of the area to be filled. Enhanced Public Routines: ========================= ? Deprecated Methods: ------------------- In the ? class: ? New samples: ------------ * ? Does ? Enhanced samples: ----------------- oodialog\?.rex Documentation: -------------- The chapter for the EventNotification class has been entirely reviewed and updated for accuracy and completeness. A detailed description for all event hanlder methods has beed added for every event connection. Known Problems, "Gotchas," and Solutions with Independent Installations ======================================================================== * Problem: The ooRexx installer creates a log of the files it installs. When the uninstaller runs, the user can select to only uninstall files logged during installtion. An indpendent ooDialog installation may install some example programs, documentation files, and shortcuts not recorded in the log file. When ooRexx is uninstalled or upgraded, these files and shortcuts may not be deleted. Solution 1: Before uninstalling ooRexx, install the independent ooDialog that matches the ooRexx installation. I.e., if the ooRexx installation is any 4.0.x, or 4.1.x ooRexx version, install the ooDialog 4.1.0 indpendent installation. Then when ooRexx is uninstalled, all ooDialog files and shortcuts will be removed because the files and shortcuts exactly match what was installed during the ooRexx installation. Solution 2: After uninstalling ooRexx, manually delete any files in the old ooRexx installation directory. * Gotcha: The independent ooDialog installation deletes the entire ooDialog samples subdirectory tree. This will delete any personal files that may have been put there after ooRexx was installed. Solution 1: Do not put personal files in the %REXX_HOME%\samples\ooDialog subdirectory tree. Solution 2: Before executing the independent ooDialog installer, move or back up any personal files that may be in %REXX_HOME%\samples\ooDialog subdirectory tree.
Source: ReadMe.txt, updated 2014-02-17

Thanks for helping keep SourceForge clean.

Screenshot instructions:
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks