[r9932]: ooDialog / trunk / doc / ooDialog_ReleaseNotes.txt Maximize Restore History

Download this file

ooDialog_ReleaseNotes.txt    373 lines (217 with data), 9.3 kB

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
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.