fxruby 1.6.40-x64-mingw32 → 1.6.41-x64-mingw32

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 4b56fdf647f9e84ab5cfb3f192b088847830851ce9fa948112775c6fa9062a26
4
- data.tar.gz: 806a9b1764e6f4ea7a97cbbed94ace2738adfb862c80bc37c92e88c1ad14c811
3
+ metadata.gz: 9ae448d281b1095f832ec354a68f3e58a03ce27f6ea7b6bb564c9427b74b2d0c
4
+ data.tar.gz: f9ef8a0623bf71a8bb5ec09682cebdef73fe79bffee3680bd59bbf79352f8fb0
5
5
  SHA512:
6
- metadata.gz: b1de84f1cd41fdf3d4ede789542b73069aff96232d7342bec9919bf5d30f429b0eb4f94ed6decc7a0589b1ca576492fdf5566c4dbd3ec700ab58309d9fb9aa62
7
- data.tar.gz: 73bdda67f95215c038918d1ea2f1a210c1d7225868fca5fa2decc8a3b79623e1513212c810c2e68b49c8be519a6d7569b44863dbad233074feb1ecc17ffe1adc
6
+ metadata.gz: 3732131cdf68df231b3b8acb289f3797c6c7fafea9da1268493ad2bd2c302487ddd925e83d5fa3e7f3c2db814528f1a3d78add05a114dcd2c6cbec5bff16c903
7
+ data.tar.gz: eba879ffda199f368d959a4b1601ad42b7021782bb57c5b0fd2dc0a57c46f80d736150ba2d6fc3747f7e5110276816ed52878de799b266b8706a8e74b0233b84
data/Gemfile CHANGED
@@ -9,10 +9,10 @@ gem 'mini_portile2'
9
9
 
10
10
  group :development do
11
11
  gem 'rake-compiler', '~> 1.0'
12
- gem 'rake-compiler-dock', '~> 0.7.0'
12
+ gem 'rake-compiler-dock', '~> 1.0'
13
13
  gem 'yard', '~> 0.8'
14
14
  gem "bundler", ">= 1.12", "< 3.a"
15
- gem "rake", "~> 12.0"
15
+ gem "rake", "~> 13.0"
16
16
  end
17
17
 
18
18
  group :test do
data/History.md CHANGED
@@ -1,4 +1,14 @@
1
- === 1.6.40 / 2018-12-28
1
+ ## 1.6.41 / 2020-01-26
2
+
3
+ * Add support for Ruby-2.7
4
+ * Fix build error on FreeBSD. #51
5
+ * Fix handling of scroll events to FXText instance.
6
+ * Add 8 virtual methods of FXText to be passed through ruby.
7
+ * FXText#findText: Return multi entry array only when searching Regex.
8
+ * Fix several example apps in example/ dir.
9
+ * Update to rake-compiler-dock-1.0 and use parallel cross build.
10
+
11
+ ## 1.6.40 / 2018-12-28
2
12
 
3
13
  * Fix some library classes which failed, when Fox was not included into the global namespace.
4
14
  * Add new accessor FXImage#dataPtr to access raw image data from FFI, Fiddle or OpenGL.
@@ -8,22 +18,22 @@
8
18
  * Add support for RubyInstaller-2.6
9
19
  * Set minimum required ruby version to 2.2.
10
20
 
11
- === 1.6.39 / 2017-12-26
21
+ ## 1.6.39 / 2017-12-26
12
22
 
13
23
  * Fix FXGLVisual.supported and .supported?
14
24
  * Add support for RubyInstaller-2.5
15
25
 
16
- === 1.6.38 / 2017-07-27
26
+ ## 1.6.38 / 2017-07-27
17
27
 
18
28
  * Update dependent libraries for Windows binary gem.
19
29
  * Replace libjpeg-9b by libjpeg-turbo-1.5.2 on Windows binary gem.
20
30
  * Fix build with clang on FreeBSD (and possibly other OS). Fixes #41
21
31
 
22
- === 1.6.37 / 2017-06-24
32
+ ## 1.6.37 / 2017-06-24
23
33
 
24
34
  * Add a 3rd type of FXRbObjects which is used for callbacks. Fixes #39
25
35
 
26
- === 1.6.36 / 2017-06-04
36
+ ## 1.6.36 / 2017-06-04
27
37
 
28
38
  * Support the fxruby source gem on Windows (only RubyInstaller-2.4).
29
39
  * Replace our self-made directory search methods by pgk-config.
@@ -33,7 +43,7 @@
33
43
  * Update to libjpeg-9b
34
44
  * More automation for gem releases
35
45
 
36
- === 1.6.35 / 2017-02-15
46
+ ## 1.6.35 / 2017-02-15
37
47
 
38
48
  * Adjust for Ruby-2.4 with unified Integers
39
49
  * Add support for RubyInstaller-2.4
@@ -44,7 +54,7 @@
44
54
  * Update dependent gems.
45
55
  * Update libraries for Windows build.
46
56
 
47
- === 1.6.34 / 2016-04-26
57
+ ## 1.6.34 / 2016-04-26
48
58
 
49
59
  * Add support for RubyInstaller-2.3
50
60
  * Avoid RARRAY_PTR() which broke fxruby on ruby-2.3.0.
@@ -52,7 +62,7 @@
52
62
  * Fix initialisation of runOnUiThread event handler, when FXApp is called with a block.
53
63
  * Disable GVL on RubyInstaller-1.9.3. Fixes #24
54
64
 
55
- === 1.6.33 / 2015-08-20
65
+ ## 1.6.33 / 2015-08-20
56
66
 
57
67
  * Avoid rb_* calls that are prohibited during GC. Fixes #23
58
68
  * Use copy'ing getters for FXVec members in FXMat*, FXMaterial and FXLight.
@@ -60,7 +70,7 @@
60
70
  * Fix test suite, so that all tests pass.
61
71
  * Add a travis-ci test setup and connect it to the github account.
62
72
 
63
- === 1.6.32 / 2015-08-07
73
+ ## 1.6.32 / 2015-08-07
64
74
 
65
75
  * Avoid call to rb_class2name() during GC. Fixes #21
66
76
  * Use release mode, unless extconf.rb is called with --enable-debug,
@@ -68,12 +78,12 @@
68
78
  * Remove self made GC detection by ruby's rb_during_gc().
69
79
  * Fix Windows binary x86-mingw32.gem for Ruby versions < 2.0
70
80
 
71
- === 1.6.31 / 2015-07-21
81
+ ## 1.6.31 / 2015-07-21
72
82
 
73
83
  * Replace pipe2() by pipe() and fcntl(), because pipe2() is not as portable.
74
84
  * Add missing include statement. Fixes #20
75
85
 
76
- === 1.6.30 / 2015-07-07
86
+ ## 1.6.30 / 2015-07-07
77
87
 
78
88
  * Fix crashes in rb_gc_mark(): 0x00000003f54af8 is T_ZOMBIE / T_NONE
79
89
  * Release Ruby's GVL while calls to FXImage#savePixels, #loadPixels
@@ -84,7 +94,7 @@
84
94
  This allows to safely execute GUI code from other threads.
85
95
  * Use rake-compiler-dock for building windows binary gems.
86
96
 
87
- === 1.6.29 / 2015-02-17
97
+ ## 1.6.29 / 2015-02-17
88
98
 
89
99
  * Add Windows binaries for Ruby-2.1 and 2.2.
90
100
  * Use shared libs for Windows binary gems to reduce gem size.
@@ -95,40 +105,40 @@
95
105
  * Change GC'ing of TreeListBox and FXTreeItem. Fixes #10
96
106
  * Update to swig version 2.0 or newer. Fixes #13
97
107
 
98
- === 1.6.28 / 2013-07-05
108
+ ## 1.6.28 / 2013-07-05
99
109
 
100
110
  * Fix build for Ruby-2.0.0-p127+
101
111
  * Update libraries for win32 build: libfox-1.6.49
102
112
 
103
- === 1.6.27 / 2013-04-05
113
+ ## 1.6.27 / 2013-04-05
104
114
 
105
115
  * Add support for Ruby-2.0.
106
116
  * Add cross compilation for x64-mingw32 target.
107
117
 
108
- === 1.6.26 / 2013-02-16
118
+ ## 1.6.26 / 2013-02-16
109
119
 
110
120
  * Mark all text strings retrieved from fox as UTF-8 when running on Ruby 1.9
111
121
  * Fix loading error on Ruby 1.8.7 by renaming the C++ extension to fox16_c
112
122
  * Update libraries for windows cross compilation
113
123
 
114
- === 1.6.25 / 2012-06-17
124
+ ## 1.6.25 / 2012-06-17
115
125
 
116
126
  * Windows: Fix slow loading of fox16.so by using a more recent mingw-w64 compiler
117
127
  (reported by Allen Doug and Igor Jorobus)
118
128
  * Fix two possible segfaults in conjunction with FXSplashWindow (reported by Igor Jorobus)
119
129
 
120
- === 1.6.24 / 2012-06-06
130
+ ## 1.6.24 / 2012-06-06
121
131
 
122
132
  * Update libraries for win32 build: libz-1.2.7 libpng-1.5.10 libjpeg-8d libtiff-4.0.1 libfox-1.6.45
123
133
  * Avoid Segfauls in lots of methods when called with nil instead of FXApp, FXComposite or FXWindow objects
124
134
 
125
- === 1.6.23 / 2012-03-08
135
+ ## 1.6.23 / 2012-03-08
126
136
 
127
137
  * Add YARD documentation support
128
138
  * Use generated Manifest.txt
129
139
  * Support for parallel task execution with drake
130
140
 
131
- === 1.6.22 / 2012-02-21
141
+ ## 1.6.22 / 2012-02-21
132
142
 
133
143
  * Allow better access to raw pixel data of FXImage and derivatives
134
144
  * Build Windows binary gem per cross compiler on Linux
@@ -147,13 +157,1295 @@
147
157
  * Fix FXApp#addInput for Ruby 1.9 on Linux
148
158
  * Fix "ruby_code case not handled: Regexp" issue with newer rubygems
149
159
 
150
- === 1.6.20 / 2009-03-06
160
+ ## Changes For Version 1.6.20 (November 09, 2009)
151
161
 
152
162
  * Integrated the Hoe and rake-compiler extensions into the Rakefile and
153
163
  removed redundant tasks.
154
164
  * Did some work to provide support for MinGW builds.
165
+ * The previous release of FXRuby couldn't be built from source against Ruby 1.9.1 final
166
+ due to a change in some of the file-related utility libraries
167
+ (see RubyForge Bug #23786). This problem has been corrected.
168
+
169
+
170
+ ## Changes For Version 1.6.19 (March 6, 2009)
171
+
172
+ * The previous release of FXRuby couldn't be built from source against Ruby 1.9.1 final
173
+ due to a change in some of the file-related utility libraries
174
+ (see RubyForge Bug #23786). This problem has been corrected.
175
+ * The previous release of FXRuby couldn't be built from source against Ruby versions 1.8.5 or
176
+ earlier (see RubyForge Bug #23967). This problem has been corrected.
177
+ * A change in the return value for Ruby's `instance_variables` method broke
178
+ some of the code related to message handling in FXRuby (see RubyForge
179
+ Bug #23787). This problem has been corrected.
180
+ * The `addAccel` method for the `FXAccelTable` class
181
+ now accepts lambda functions (or any other objects that respond to `call`). See
182
+ the API documentation
183
+ for `FXAccelTable` for examples of how this works.
184
+
185
+
186
+ ## Changes For Version 1.6.18 (December 29, 2008)
187
+
188
+ * Some users were having trouble building FXRuby on 64-bit operating systems
189
+ (see RubyForge Bug #23375). This problem has been corrected.
190
+
191
+
192
+ ## Changes For Version 1.6.17 (December 24, 2008)
193
+
194
+ * The Ruby interpreter was generating a large number of warning messages about redefined methods
195
+ in the `kwargs.rb` library
196
+ (see RubyForge
197
+ Bug #19231 and elsewhere). This problem has been corrected.
198
+
199
+ * Due to recent changes in Ruby's garbage collection algorithm, FXRuby applications could under some circumstances
200
+ crash for large numbers of table items
201
+ (see RubyForge bugs ).
202
+ This bug has been fixed.
203
+
204
+ * The documentation for the `FXTable` class referred to the non-existent `setColumnX`
205
+ and `setRowY` instance methods
206
+ (see RubyForge
207
+ Bug #21987). These entries have been removed from the documentation.
208
+
209
+ * A number of instance methods for the `FXTable` class could crash an application if they
210
+ were passed out-of-bounds index arguments
211
+ (see RubyForge
212
+ Bug #21987). These methods now raise `IndexError` when they're passed out-of-bounds
213
+ indexes.
214
+
215
+ * Due to a change in the URL scheme for the Dilbert web site, the `dilbert.rb` example
216
+ program was no longer working properly
217
+ (see RubyForge
218
+ Bug #21538). This has been fixed.
219
+
220
+ * The `lower` method for the `FXRangef` was returning
221
+ ´self´ instead of an `FXVec3f` instance for the range's low
222
+ bound
223
+ (see RubyForge
224
+ Bug #22488). This has been fixed.
225
+
226
+ * Made a number of minor fixes for compatibility with Ruby 1.9.1.
227
+
228
+
229
+ ## Changes For Version 1.6.16 (July 3, 2008)
230
+
231
+ * Historically, if you called `create` on a
232
+ window before its parent window was created, your application would
233
+ crash (see RubyForge
234
+ Bug #20702 and elsewhere). Now, the code should raise a
235
+ ´RuntimeError´ with a message indicating the
236
+ problem.
237
+
238
+ * The message data that the `FXPicker` widget
239
+ sends along with its ´SEL_CHANGED´ and
240
+ ´SEL_COMMAND´ messages wasn't being handled
241
+ properly, and as a result, applications using this widget could crash
242
+ (see RubyForge
243
+ Bug #20780). This problem has been fixed.
244
+
245
+
246
+ ## Changes For Version 1.6.15 (June 4, 2008)
247
+
248
+ * FXRuby applications could crash (with a segmentation fault) if
249
+ ´nil´ was passed in as the first argument to
250
+ `FXDialogBox.new` or
251
+ `FXMainWindow.new` (see RubyForge
252
+ Bug #14642). These methods now raise an
253
+ ´ArgumentError´ if ´nil´ is
254
+ passed as the first argument.
255
+
256
+ * You should only ever construct one `FXApp`
257
+ object per application, but there was no protection against doing so
258
+ in the code (see RubyForge
259
+ Bug #16275). Now, `FXApp.new` will
260
+ raise a `RuntimeException` if an
261
+ `FXApp` object already exists.
262
+
263
+ * The `babelfish.rb` example program, which
264
+ previously depended on an external web service to perform translation
265
+ between languages, was broken since that web service no longer exists
266
+ (see RubyForge
267
+ Bug #16962). The example has now been updated to use Dr. Nic's
268
+ Tranexp library instead.
269
+
270
+ * The value of the ´MBOX_SAVE_CANCEL_DONTSAVE´
271
+ option (for the `FXMessageBox` class) wasn't
272
+ wrapped properly and was unusable (see RubyForge
273
+ Bug #17094). There was also no constant corresponding to the
274
+ ´MBOX_CLICKED_DONTSAVE´ return value. Both of these
275
+ problems have been fixed.
276
+
277
+ * The fields for new `FXHiliteStyle` objects
278
+ were uninitialized and as a result sometimes gave unpredictable
279
+ results (see RubyForge
280
+ Bug #19637). This has been fixed.
281
+
282
+ * The `columnHeaderFont` and
283
+ `rowHeaderFont` attributes for
284
+ `FXTable` weren't implemented properly (see
285
+ RubyForge
286
+ Bug #20142). This has been fixed.
287
+
288
+ * Ruby 1.8.7 adds a new `first` method to
289
+ the `Enumerable` module, and this conflicts with
290
+ the existing `first` method defined in the
291
+ `FXWindow` base class for a number of FXRuby
292
+ classes which mix in `Enumerable` (see RubyForge
293
+ Bug #20418). This problem has been resolved.
294
+
295
+ * Due to a bug in the `extconf.rb` script, the
296
+ build was failing for Ruby 1.9.0 (see RubyForge
297
+ Bug #20426). This has been fixed.
298
+
299
+
300
+ ## Changes For Version 1.6.14 (March 29, 2008)
301
+
302
+ * Updated the documentation for the `FXImage`
303
+ class to indicate which methods call `render`
304
+ after they're finished, and which ones do not.
305
+
306
+ * Corrected a little typo in the
307
+ `gembrowser.rb` example program.
308
+
309
+ * Updated the `dilbert.rb` example program to
310
+ use the more popular-and-likely-to-be-installed Hpricot HTML
311
+ parser library instead of Rubyful Soup.
312
+
313
+ * Re-added the documentation for the
314
+ ´TOGGLEBUTTON_KEEPSTATE´ option, which had
315
+ mysteriously disappeared (see RubyForge
316
+ Bug #2286).
317
+
318
+ * Made a number of minor fixes to support building FXRuby against
319
+ Ruby 1.9.
320
+
321
+ * Added a binary gem for OS X. This works with the Ruby that's
322
+ included with OS X (Leopard).
323
+
324
+ * The binary gem for Windows was built with FOX version 1.6.32 and
325
+ FXScintilla version 1.71.
326
+
327
+
328
+ ## Changes For Version 1.6.13 (November 9, 2007)
329
+
330
+ * Calls to the `extractText` method for the
331
+ `FXTable` class were causing various
332
+ memory-related errors on certain platforms (see RubyForge
333
+ Bug #15444). This problem has been fixed.
334
+
335
+ * The binary gem for Windows was built with FOX version 1.6.28 and
336
+ FXScintilla version 1.71.
337
+
338
+ ## Changes For Version 1.6.12 (October 19, 2007)
339
+
340
+ * The API documentation for `FXMDIClient`
341
+ referred to the non-existent instance method
342
+ `activeChild=` (see RubyForge
343
+ Bug #10259). This method has been added.
344
+
345
+ * The API documentation for `FXMDIClient`
346
+ also referred to the non-existent instance methods
347
+ `getMDIChildFirst` and
348
+ `getMDIChildLast`. These entries have been
349
+ removed.
350
+
351
+ * The API documentation for `FXMDIChild`
352
+ referred to non-existent instance methods
353
+ `getMDINext` and
354
+ `getMDIPrev` (see RubyForge
355
+ Bug #10436). The documentation has been corrected.
356
+
357
+ * Added the ´:repeat´ parameter for the
358
+ `addChore` and
359
+ `addTimeout` methods. See the documentation for
360
+ more details, and `gltest.rb` for an example of its
361
+ use.
362
+
363
+ * Corrected a number of minor typos in the API
364
+ documentation.
365
+
366
+ * Corrected a typo in the `imageviewer.rb`
367
+ example.
368
+
369
+ * Modified the `inputs.rb` example program to
370
+ use `Pipe.read_nonblock()` instead of
371
+ `Pipe.read()`.
372
+
373
+ * Fixed a bug in the implementation of the
374
+ `findText` method for the
375
+ `FXText` class, when used with the
376
+ ´SEARCH_REGEX´ option.
377
+
378
+ * The binary gem for Windows was built with FOX version 1.6.28 and
379
+ FXScintilla version 1.71.
380
+
381
+
382
+ ## Changes For Version 1.6.11 (April 18, 2007)
383
+
384
+ * Added `editable` as an alias for
385
+ `FXTextField#editable?`.
386
+
387
+ * Added `each_child_recursive` instance
388
+ method for the `FXWindow` class. This method
389
+ performs a depth-first traversal of the widget tree starting at the
390
+ receiver window.
391
+
392
+ * Corrected some errors in the keyword arguments support for the
393
+ `FXVec2d`, `FXVec2f`,
394
+ `FXVec3d`, `FVec3f`,
395
+ `FXVec4d` and `FXVec4f`
396
+ classes.
397
+
398
+ * Corrected an error in the keyword arguments support for the
399
+ `FXIconDict` class.
400
+
401
+ * Modified the gem specification so that the RDoc generated during
402
+ a gem install is consistent with that generated by other methods (see
403
+ RubyForge
404
+ Bug #10035).
405
+
406
+ * Changes to the `iterators` library in version
407
+ 1.6.6 introduced a bug in the `each` method for
408
+ the `FXFoldingList`,
409
+ `FXTreeList` and
410
+ `FXTreeListBox` classes (see RubyForge
411
+ Bug #10175). This problem has been fixed.
412
+
413
+ * Applied submitted patches for building FXRuby against Ruby 1.9
414
+ (see RubyForge
415
+ Bug #10181). Please note that building FXRuby against the Ruby
416
+ 1.9 code base is still officially unsupported; however, I'm glad to
417
+ accept patches that will help make this possible.
418
+
419
+ * The binary gem for Windows was built with FOX version 1.6.25 and
420
+ FXScintilla version 1.71.
421
+
422
+
423
+ ## Changes For Version 1.6.9 (April 8, 2007)
424
+
425
+ * A bug was discovered in the keyword arguments library support
426
+ for the `FXMenuBar` class (see RubyForge
427
+ Bug #9927). This problem has been fixed.
428
+
429
+ * The binary gem for Windows was built with FOX version 1.6.25 and
430
+ FXScintilla version 1.71.
431
+
432
+
433
+ ## Changes For Version 1.6.8 (April 5, 2007)
434
+
435
+ * Due to an internal bookkeeping error, applications like the
436
+ `glviewer.rb` example program which create multiple
437
+ `FXGLViewer` instances could cause an assertion
438
+ to fail. When this assertion fails on Windows, the program simply
439
+ crashes (see RubyForge
440
+ Bug #9775). This problem has been fixed.
441
+
442
+ * The keyword arguments library, introduced in version 1.6.5, is
443
+ now included automatically when you load FXRuby; it is no longer
444
+ necessary to explicitly require it.
445
+
446
+ * The binary gem for Windows was built with FOX version 1.6.25 and
447
+ FXScintilla version 1.71.
448
+
449
+
450
+ ## Changes For Version 1.6.7 (March 31, 2007)
451
+
452
+ * The binary gem for Windows was built with FOX version 1.6.25 and
453
+ FXScintilla version 1.71.
454
+
455
+
456
+ ## Changes For Version 1.6.6 (February 10, 2007)
457
+
458
+ * Somewhere along the way, the RAA browser example program got
459
+ broken due to changes in the SOAP interface to RAA (see RubyForge
460
+ Bug #7977). This has been fixed.
461
+
462
+ * Some debugging code that was meant to detect errors in FXRuby
463
+ message data conversion was inadvertently causing some user
464
+ applications to crash when running under Windows (see RubyForge
465
+ Bug #8049). This debugging code has been changed to avoid the
466
+ problem.
467
+
468
+ * Modified the implementations of the each iterator methods for
469
+ `FXFoldingList`,
470
+ `FXFoldingItem`,
471
+ `FXTreeItem`, `FXTreeList`
472
+ and `FXTreeListBox` (see RubyForge
473
+ Bug #8090). The new implementation is a bit more robust in
474
+ terms of modifications (such as deletion) of the iterated-over
475
+ elements.
476
+
477
+ * A bug in the new keyword arguments library (introduced in
478
+ version 1.6.5) caused the `initialize` method
479
+ for the `FXDCWindow` class to do the wrong thing
480
+ (see RubyForge
481
+ Bug #8441). This has been corrected.
482
+
483
+ * A different bug in the keyword arguments library caused the
484
+ `initialize` method for the
485
+ `FXFont` class to do the wrong thing (see RubyForge
486
+ Bug #8517). This also has been corrected.
487
+
488
+ * Yet another bug in the keyword arguments library broke the part
489
+ of the code that used to yield ´self´ to an
490
+ optional block attached to the call to `new`
491
+ (see RubyForge
492
+ Bug #8518). This has been corrected.
493
+
494
+ * Most of the FXRuby example programs have been updated to use the
495
+ keyword arguments library.
496
+
497
+ * Added a new "virtual" keyword argument
498
+ ´:padding´ that can be used in place of (or in
499
+ addition to) the ´:padLeft´,
500
+ ´:padRight´, ´:padTop´ and
501
+ ´:padBottom´ arguments for a constructor. When a
502
+ ´:padding´ value is passed in to the arguments
503
+ hash, that value will be used for any of the four regular padding
504
+ values that aren't otherwise specified. See the example programs for,
505
+ you know, examples.
506
+
507
+ * The binary gem for Windows was built with FOX version 1.6.20 and
508
+ FXScintilla version 1.71.
509
+
510
+
511
+ ## Changes For Version 1.6.5 (January 20, 2007)
512
+
513
+ * Clicking outside of the visible cells for an
514
+ `FXTable` when there was no current selection
515
+ caused the code to raise an exception (see RubyForge
516
+ Bug #5907). This problem has been fixed.
517
+
518
+ * The `hasTimeout?` method for the
519
+ `FXApp` class was implemented incorrectly (see
520
+ RubyForge
521
+ Bug #7564). This problem has been fixed.
522
+
523
+ * The `FXFoldingList` and
524
+ `FXFoldingItem` classes did not have each
525
+ iterator methods like most of the other list-based widgets (see RubyForge
526
+ Patch #7978). These have been added.
527
+
528
+ * The API documentation for `FXMDIClient`
529
+ claimed that `FXScrollArea` was its base class
530
+ (see RubyForge
531
+ Bug #7979). This has been corrected; the base class for
532
+ `FXMDIClient` is
533
+ `FXComposite`.
534
+
535
+ * There was a small typo in the documentation for the
536
+ `FXFoldingList` class options (see RubyForge
537
+ Bug #7981). This has been fixed.
538
+
539
+ * Added preliminary support for keyword-style arguments, as
540
+ described in the "Differences Between
541
+ FOX and FXRuby" section of the FXRuby User's Guide.
542
+
543
+ * The binary gem for Windows was built with FOX version 1.6.20 and
544
+ FXScintilla version 1.71.
545
+
546
+
547
+ ## Changes For Version 1.6.4 (November 30, 2006)
548
+
549
+ * A change made in Ruby 1.8.5 for cyclic requires led to a problem
550
+ that caused the Ruby interpreter to emit a large number of warnings
551
+ (see RubyForge
552
+ Bug #5633). This problem has been fixed.
553
+
554
+ * The binary gem for Windows was built with FOX version 1.6.16 and
555
+ FXScintilla version 1.71.
556
+
557
+
558
+ ## Changes For Version 1.6.3 (October 27, 2006)
559
+
560
+ * Widgets of some classes (namely
561
+ `FXTopWindow` and
562
+ `FXMDIChild`) weren't properly sending a
563
+ ´SEL_CLOSE´ message to their message targets (see
564
+ RubyForge
565
+ Bug #5498). Thanks to a change in FOX version 1.6.16, this
566
+ problem has been fixed.
567
+
568
+ * The `getControlFor` method for the
569
+ `FXComboTableItem` class was coded incorrectly
570
+ (see RubyForge
571
+ Bug #5906). This has been fixed.
572
+
573
+ * There was a minor typo in the API documentation for the
574
+ `FXTriStateButton` class (see RubyForge Bug #5962). This has been fixed.
575
+
576
+ * The `each_row` and
577
+ `each_column` iterator methods for the
578
+ `FXTable` class were incorrectly coded (see
579
+ RubyForge
580
+ Bug #6036). This has been fixed.
581
+
582
+ * The `new` class methods for
583
+ `FXColorItem`, `FXDirItem`,
584
+ `FXFileItem`,
585
+ `FXFoldingItem`,
586
+ `FXHeaderItem`,
587
+ `FXIconItem`, `FXListItem`
588
+ and `FXTreeItem` were all raising exceptions when
589
+ a non-´nil´ value was passed in for the last
590
+ argument (see RubyForge
591
+ Bug #6197). A similar problem was present for various instance
592
+ methods in the `FXColorList`,
593
+ `FXListBox` and
594
+ `FXMDIClient` classes. These problems have been
595
+ fixed.
596
+
597
+ * A few problems were discovered for the
598
+ `inputs.rb` example program (see RubyForge
599
+ Bug #6209). These problems have been fixed.
600
+
601
+ * Several instance methods for the `FXTable`
602
+ class were not actually present under their documented names (see
603
+ RubyForge
604
+ Bug #6211). This has been fixed.
605
+
606
+ * The build script was not compatible with changes made in the
607
+ recently-released FXScintilla 1.71 (see RubyForge
608
+ Bug #6313). This has been fixed.
609
+
610
+ * The binary gem for Windows was built with FOX version 1.6.16 and
611
+ FXScintilla version 1.71.
612
+
613
+
614
+ ## Changes For Version 1.6.2 (September 13, 2006)
615
+
616
+ * The `expandTree()` and
617
+ `collapseTree()` methods for the
618
+ `FXFoldingList` class were incorrectly identified
619
+ as `expandFolding()` and
620
+ `collapseFolding()` in the API documentation
621
+ (see RubyForge
622
+ Bug #5354). This has been fixed.
623
+
624
+ * The `FXDockTitle` class was not supported
625
+ (see RubyForge
626
+ Bug #5632). This has been fixed.
627
+
628
+ * The API documentation for the `FXGLCanvas`
629
+ class claimed it had a `shared?` method, but it
630
+ didn't (see RubyForge
631
+ Bug #5591). Now it does.
632
+
633
+ * The `FXGradientBar` class was not supported
634
+ (see RubyForge
635
+ Bug #5746). This has been fixed.
636
+
637
+ * The binary gem for Windows was built with FOX version 1.6.14 and
638
+ FXScintilla version 1.67 (from CVS).
639
+
640
+
641
+ ## Changes For Version 1.4.7 (September 13, 2006)
642
+
643
+ * The `children` instance method for the
644
+ `FXWindow` class always returned an array of
645
+ `FXWindow` instances, even if the actual types
646
+ should have been instances of subclasses of
647
+ `FXWindow` (see RubyForge
648
+ Bug #4342). This has been fixed.
649
+
650
+ * The `dilbert.rb` example program was broken
651
+ due to a change in the Dilbert.com web site structure (see RubyForge
652
+ Bug #4597). This has been fixed.
653
+
654
+ * The `expandTree()` and
655
+ `collapseTree()` methods for the
656
+ `FXFoldingList` class were incorrectly identified
657
+ as `expandFolding()` and
658
+ `collapseFolding()` in the API documentation
659
+ (see RubyForge
660
+ Bug #5354). This has been fixed.
661
+
662
+ * The `FXDockTitle` class was not supported
663
+ (see RubyForge
664
+ Bug #5632). This has been fixed.
665
+
666
+ * The API documentation for the `FXGLCanvas`
667
+ class claimed it had a `shared?` method, but it
668
+ didn't (see RubyForge
669
+ Bug #5591). Now it does.
670
+
671
+ * The `FXGradientBar` class was not supported
672
+ (see RubyForge
673
+ Bug #5746). This has been fixed.
674
+
675
+ * The binary gem for Windows was built with FOX version 1.4.34 and
676
+ FXScintilla version 1.63.
677
+
678
+
679
+ ## Changes For Version 1.6.1 (July 21, 2006)
680
+
681
+ * The message data sent along for the
682
+ ´SEL_INSERTED´, ´SEL_DELETED´
683
+ and ´SEL_REPLACED´ messages from an a
684
+ `FXText` widget to its target was not being
685
+ converted properly (see RubyForge
686
+ Bug #4666). This has been fixed.
687
+
688
+ * The code related to the localization of application messages in
689
+ FOX wasn't implemented properly in FXRuby, and as a result,
690
+ constructing certain dialogs (like the color dialog) could cause a
691
+ program to crash (see RubyForge
692
+ Bug #5000). This has been fixed.
693
+
694
+ * The "Stop Spin" button in the gltest.rb example program didn't
695
+ stop the cubes from spinning after either the "Spin Timer" or "Spin
696
+ Chore" option was selected (see RubyForge
697
+ Bug #5001). This was actually a symptom of a larger problem,
698
+ that FXRuby wasn't properly handling timers and chores. These problems
699
+ have been fixed.
700
+
701
+ * Setting the current item for an
702
+ `FXComboBox` to -1 (to indicate that there's no
703
+ current item) would cause FXRuby to erroneously raise an
704
+ `IndexError` (see RubyForge
705
+ Bug #5007). This has been fixed.
706
+
707
+ * The documentation for the `reparent`
708
+ instance method for the `FXWindow` class was
709
+ incorrect (see RubyForge
710
+ Bug #5035). This has been fixed.
711
+
712
+ * The `textedit.rb` example program was not up
713
+ to date with some of the changes for FOX 1.6. This example has been
714
+ updated.
715
+
716
+ * The new `font` method for the
717
+ `FXFont` class was not documented. This has been
718
+ fixed.
719
+
720
+ * The `dilbert.rb` example program has been
721
+ modified to use the RubyfulSoup HTML library instead of the
722
+ html-parser library.
723
+
724
+ * As discussed in various forums (see for example [this
725
+ post](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/182827), the `autorequire` directive for
726
+ RubyGems specifications is now deprecated. As a result, this has been
727
+ removed from the FXRuby gem specification. This change will break any
728
+ code that was using a statement like:´require_gem 'fxruby'´as
729
+ the sole means for loading FXRuby. Such programs should instead
730
+ use:´require 'fox16'´which will work
731
+ for either gem based or non-gem based installations.
732
+
733
+ * The binary gem for Windows was built with FOX version 1.6.8 and
734
+ FXScintilla version 1.67 (from CVS).
735
+
736
+
737
+ ## Changes For Version 1.6.0 (May 29, 2006)
738
+
739
+ * This is the first release of FXRuby compatible with FOX version
740
+ 1.6. One of the most signficant changes for FOX 1.6 has been the
741
+ addition of Unicode support; all FOX widgets and internal string
742
+ processing routines are now Unicode aware. For a comprehensive
743
+ overview of the changes made to FOX since version 1.4 (including those
744
+ made in the FOX 1.5 development series), please refer to the
745
+ [News archives](http://www.fox-toolkit.com/news.html) at
746
+ the FOX web site.
747
+
748
+ * Added the `allowSide`,
749
+ `disallowSide` and
750
+ `allowedSide?` methods for the
751
+ `FXDockBar` class, as complements to the
752
+ `allowedSides` accessor methods (see RubyForge
753
+ Feature Request #2307).
754
+
755
+ * Added the `visible=` and
756
+ `visible?` accessor methods for the
757
+ `FXWindow` class, as complements to the
758
+ `show`, `hide` and
759
+ `shown?` methods (see RubyForge
760
+ Feature Request #3579).
761
+
762
+ * The `browser.rb` example was making use of a
763
+ deprecated API (see RubyForge
764
+ Bug #4325). This has been fixed.
765
+
766
+ * The `children` instance method for the
767
+ `FXWindow` class always returned an array of
768
+ `FXWindow` instances, even if the actual types
769
+ should have been instances of subclasses of
770
+ `FXWindow` (see RubyForge
771
+ Bug #4342). This has been fixed.
772
+
773
+ * The `dilbert.rb` example program was broken
774
+ due to a change in the Dilbert.com web site structure (see RubyForge
775
+ Bug #4597). This has been fixed.
776
+
777
+ * The binary gem for Windows was built with FOX version 1.6.5 and
778
+ FXScintilla version 1.67 (from CVS).
779
+
780
+
781
+ ## Changes For Version 1.4.6 (April 26, 2006)
782
+
783
+ * FXRuby would not compile properly on some x86-64 systems (see
784
+ RubyForge
785
+ Bug #3729). This error has been corrected. Thanks to Javier
786
+ Goizueta for initially reporting this problem, and especially to
787
+ Tobias Peters for providing a patch.
788
+
789
+ * The `FXIconDict` widget was accidentally
790
+ "lost" in the transition between FXRuby versions 1.2 and 1.4 (see
791
+ RubyForge
792
+ Bug #4117). This error has been corrected. Thanks to Manfred
793
+ Usselmann for reporting this problem.
794
+
795
+ * The `FXSwitcher` widget was not sending the
796
+ appropriate message data to its message target for the
797
+ ´SEL_COMMAND´ message type (see RubyForge
798
+ Bug #4157). This error has been corrected. Thanks to Manfred
799
+ Usselmann for reporting this problem.
800
+
801
+ * The `FXSeparator` class wasn't implemented
802
+ properly (see RubyForge
803
+ Bug #4158). This error has been corrected. Thanks to Gerard
804
+ Menochet for reporting this problem.
805
+
806
+ * The `findItemByData` method was
807
+ implemented incorrectly for the `FXComboBox`,
808
+ `FXFoldingList`,
809
+ `FXIconList`, `FXList` and
810
+ `FXListBox` classes (see RubyForge
811
+ Bug #4172). This error has been corrected. Thanks to Gerard
812
+ Menochet for reporting this problem.
813
+
814
+ * The `FXListBox` widget was not sending the
815
+ appropriate message data to its message target for the
816
+ ´SEL_COMMAND´ message type (see RubyForge
817
+ Bug #4255). This error has been corrected. Thanks to Gerard
818
+ Menochet for reporting this problem.
819
+
820
+ * The binary gem for Windows was built with FOX version 1.4.29 and
821
+ FXScintilla version 1.63.
822
+
823
+
824
+ ## Changes For Version 1.4.5 (April 10, 2006)
825
+
826
+ * The `FXTextField` class was not properly
827
+ responding to the ´ID_INSERT_STRING´ command (see
828
+ RubyForge
829
+ Bug #3320). This error has been corrected. Thanks to Uwe Hartl
830
+ for reporting this problem.
831
+
832
+ * The `text` and
833
+ `getText` methods for the
834
+ `FXMenuCaption` class were returning
835
+ ´nil´ instead of the actual value (see RubyForge
836
+ Bug #3458). This error has been corrected. Thanks to Meinrad
837
+ Recheis (Henon) for reporting this problem.
838
+
839
+ * The API documentation for the `FXMDIChild`
840
+ class erroneously listed ´SEL_CLOSEALL´ as one of
841
+ the message types that an MDI child window might send to its message
842
+ target (see RubyForge
843
+ Bug #3508). This error has been corrected. Thanks to Meinrad
844
+ Recheis (Henon) for reporting this problem.
845
+
846
+ * Calling the `selectRange` method for
847
+ class `FXTable` would cause a fatal error instead
848
+ of merely raising an `IndexError` exception (see
849
+ RubyForge
850
+ Bug #3615). This error has been corrected. Thanks to Meinrad
851
+ Recheis (Henon) for reporting this problem.
852
+
853
+ * Due to an error in the SWIG interface files, the
854
+ `FXChoiceBox` class was basically unusable (see
855
+ RubyForge
856
+ Bug #3676). This error has been corrected. Thanks to Uwe Hartl
857
+ for reporting this problem.
858
+
859
+ * The API documentation for the
860
+ `FXRealSlider` and
861
+ `FXRealSpinner` classes erroneously claimed that
862
+ the message data for the ´SEL_COMMAND´ and
863
+ ´SEL_CHANGED´ messages sent by these widgets to
864
+ their targets were integers (see RubyForge
865
+ Bug #3749). Along the same lines, the message data for those
866
+ widgets wasn't being converted correctly (see RubyForge
867
+ Bug #3750). Both of these errors have been corrected. Thanks
868
+ to Meinrad Recheis (Henon) for reporting these problems.
869
+
870
+ * The API documentation for the Fox module incorrectly listed the
871
+ names of the `FXSELTYPE` and
872
+ `FXSELID` methods as
873
+ `SELTYPE` and `SELID`
874
+ (see RubyForge
875
+ Bug #3940). This error has been corrected. Thanks to Joel
876
+ VanderWerf for reporting this problem.
877
+
878
+ * The `FXTableItem` constructor was supposed
879
+ to (optionally) accept a reference to an arbitrary Ruby object as its
880
+ third argument, but this wasn't working properly (see RubyForge
881
+ Bug #4005). This error has been corrected. Thanks to Mark
882
+ Volkman for reporting this problem.
883
+
884
+ * The binary gem for Windows was built with FOX version 1.4.29 and
885
+ FXScintilla version 1.63.
886
+
887
+
888
+ ## Changes For Version 1.4.4 (January 21, 2006)
889
+
890
+ * The build instructions for Unix platforms had not been updated
891
+ recently and as such contained some errors (see RubyForge
892
+ Bug #3014). These errors have been corrected. Thanks to Dave
893
+ Burns for reporting this problem.
894
+
895
+ * The `extendSelection` method for the
896
+ `FXTable` class was raising an exception if an
897
+ out of bounds row or column index was passed in (see RubyForge
898
+ Bug #3050). This has been changed so that
899
+ `extendSelection` instead returns false for out
900
+ of bounds arguments. Thanks to Leonid Moiseichuk for reporting this
901
+ problem.
902
+
903
+ * The `each_child` iterator method for the
904
+ `FXWindow` class would fail if the child window
905
+ was destroyed in the block (see RubyForge
906
+ Bug #3134). Thanks to Liam Irish for reporting this problem
907
+ and providing a patch.
908
+
909
+ * The message data for the ´SEL_REPLACED´
910
+ message sent by the `FXTable` class to its target
911
+ was not being handled properly (see RubyForge
912
+ Bug #3244). There were also problems with the message data for
913
+ the ´SEL_SELECTED´ and
914
+ ´SEL_DESELECTED´ messages. Furthermore, the
915
+ ´SEL_REPLACED´ message was not documented in the
916
+ RDoc documentation for the `FXTable` class. All
917
+ of these problems have been corrected. Thanks to _blackdog for
918
+ reporting this problem.
919
+
920
+ * The binary gem for Windows was built with FOX version 1.4.29 and
921
+ FXScintilla version 1.63.
922
+
923
+
924
+ ## Changes For Version 1.4.3 (November 7, 2005)
925
+
926
+ * The ´TOGGLEBUTTON_KEEPSTATE´ option for the
927
+ `FXToggleButton` class was not documented (see
928
+ RubyForge
929
+ Bug #2286). This oversight has been corrected. Thanks to Tim
930
+ Smith for reporting this problem.
931
+
932
+ * The `scintilla.rb` library file was not up to
933
+ date with the latest FXScintilla release, and as a result it was
934
+ missing some methods (see RubyForge
935
+ Bug #2479). This oversight has been corrected. Thanks to Maxim
936
+ Kulkin for reporting this problem.
937
+
938
+ * Due to changes in the APIs for timers and chores, the mechanisms
939
+ for removing chores and timeouts were broken (see RubyForge
940
+ Bug #2563). This bug has been fixed. Thanks to "moinker" for
941
+ reporting this problem.
942
+
943
+ * An error in the test setup caused all of the tests for the
944
+ `FXList` class to fail (see RubyForge
945
+ Bug #2564). This bug has been fixed. Thanks to Peter for
946
+ reporting this problem.
947
+
948
+ * Due to a bug in the test suite runner script, not all test cases
949
+ were being exercised (see RubyForge
950
+ Bug #2565). This bug has been fixed.
951
+
952
+ * Calling the `getPixel` method for the
953
+ `FXImage` class when the client-side pixel buffer
954
+ for the image has already been released would cause a program to crash
955
+ (see RubyForge
956
+ Bug #2611). Now, `getPixel` will raise
957
+ an exception if it's called after the pixel buffer has been released.
958
+ The documentation for `getPixel` has been
959
+ updated accordingly. Thanks to Gonzalo Garramuno for reporting this
960
+ problem.
961
+
962
+ * The `makePositionVisible` method for the
963
+ `FXTable` class was raising an exception when
964
+ passed out-of-bounds values for the row or column index (see RubyForge
965
+ Bug #2660). This could happen, for example, if you were to
966
+ click in a table area outside of the regular cells (which indirectly
967
+ triggers a call to `makePositionVisible`). This
968
+ was actually inconsistent with standard FOX behavior, which simply
969
+ ignores out of bounds values for that method's arguments. This bug has
970
+ been fixed, and the documentation for
971
+ `makePositionVisible` has been updated
972
+ accordingly. Thanks to Ralf Jonas for reporting this problem.
973
+
974
+ * The binary gem for Windows was built with FOX version 1.4.21 and
975
+ FXScintilla version 1.63.
976
+
977
+
978
+ ## Changes For Version 1.4.2 (August 22, 2005)
979
+
980
+ * Due to a bug in the implementation, the
981
+ `checked?` method for the
982
+ `FXCheckButton` class always returned
983
+ ´false´ (see RubyForge
984
+ Bug #1852). This bug has been fixed. Thanks to Meinrad Recheis
985
+ for reporting this problem.
986
+
987
+ * The API documentation for the `FXTable`
988
+ class listed several obsolete attributes (see RubyForge
989
+ Bug #1928). Those errors have been corrected. Thanks to Pavel
990
+ Sokolov for reporting these problems.
991
+
992
+ * There were a number of bugs in the
993
+ `textedit.rb` example program (see RubyForge
994
+ Bug #1979), and those bugs have been fixed. Thanks to Claude
995
+ Marinier for reporting these problems.
996
+
997
+ * The API documentation for the `FXTreeList`
998
+ class' `new` method still showed the number of
999
+ visible items (´nvis´) as its second argument
1000
+ (see RubyForge
1001
+ Bug #2171). This problem has been corrected. Thanks to Bill
1002
+ Atkins for reporting this problem.
1003
+
1004
+ * The API documentation for the `FXTopWindow`
1005
+ class had a number of errors (see RubyForge
1006
+ Bug #2269). This problem has been corrected.
1007
+
1008
+ * The API documentation for the `FXTreeList`
1009
+ class still listed the obsolete `reparentItem`
1010
+ method (see RubyForge
1011
+ Bug #2270). This problem has been corrected. Thanks to Jacob
1012
+ Hansen for reporting this problem.
1013
+
1014
+ * Due to a bug in how the SWIG typemaps for the
1015
+ ´FXlong´ type were defined, some methods for the
1016
+ `FXFileStream` class were broken (see RubyForge
1017
+ Bug #2275). This problem has been corrected. Thanks to Gonzalo
1018
+ Garramuno for reporting this problem.
1019
+
1020
+ * Merged in all of the fixes for FXRuby 1.2.6.
1021
+
1022
+ * The binary gem for Windows was built with FOX version 1.4.17 and
1023
+ FXScintilla version 1.63.
1024
+
1025
+
1026
+ ## Changes For Version 1.4.1 (August 20, 2005)
1027
+
1028
+ * This is the second release of FXRuby which is compatible with
1029
+ FOX 1.4, and as such should be considered an "unstable" release. For a
1030
+ history of the changes made during the FOX 1.3 and 1.4 development,
1031
+ see the [News](http://www.fox-toolkit.com/news.html)
1032
+ page at the FOX Web site.
1033
+
1034
+ * The unit tests (in the `tests` subdirectory)
1035
+ had not been updated to require the ´fox14´
1036
+ feature, and were still looking at ´fox12´. This
1037
+ has been corrected.
1038
+
1039
+ * A number of minor problems were corrected for the Windows build
1040
+ of FXRuby.
1041
+
1042
+ * The binary gem for Windows was built with FOX version 1.4.17 and
1043
+ FXScintilla version 1.63.
1044
+
1045
+
1046
+ ## Changes For Version 1.4.0 (August 19, 2005)
1047
+
1048
+ * This is the first release of FXRuby which is compatible with FOX
1049
+ 1.4, and as such should be considered an "unstable" release. For a
1050
+ history of the changes made during the FOX 1.3 and 1.4 development,
1051
+ see the [News](http://www.fox-toolkit.com/news.html)
1052
+ page at the FOX Web site.
1053
+
1054
+
1055
+ ## Changes For Version 1.2.6 (April 15, 2005)
1056
+
1057
+ * Some additional problems related to calling the
1058
+ `setTableSize` method for an
1059
+ `FXTable` were discovered (see RubyForge
1060
+ Bug #1597). This problem has been corrected. Thanks to Joel
1061
+ VanderWerf for reporting this problem.
1062
+
1063
+ * The `iconlist.rb` example program had a
1064
+ "Sort" pulldown menu filled with a number of commands that didn't
1065
+ really do anything, including sorting the items (see RubyForge
1066
+ Bug #1654). This pulldown menu has been removed from that
1067
+ example.
1068
+
1069
+ * The API documentation for the `FXDC` class
1070
+ erroneously referred to the `font` attribute as
1071
+ `textFont` (see RubyForge
1072
+ Bug #1667). This problem has been corrected. Thanks to Meinrad
1073
+ Recheis for reporting this problem.
1074
+
1075
+ * The `checked?`,
1076
+ `unchecked?` and
1077
+ `maybe?` methods for the
1078
+ `FXMenuCheck` class were missing (see RubyForge
1079
+ Bug #1677). This problem has been corrected. Thanks to Oliver
1080
+ Smith for reporting this problem.
1081
+
1082
+ * The API documentation for the
1083
+ `FXScrollArea` class incorrectly spelled the
1084
+ names of the `horizontalScrollBar` and
1085
+ `verticalScrollBar` methods as
1086
+ `horizontalScrollbar` and
1087
+ `verticalScrollbar` (see RubyForge
1088
+ Bug #1678). The documentation has been corrected. Thanks to
1089
+ Jannis Pohlmann for reporting this mistake.
1090
+
1091
+ * Some code in the `groupbox.rb` example
1092
+ program was calling the `getRootWindow` method,
1093
+ but that method has been renamed to `getRoot`
1094
+ (see RubyForge
1095
+ Bug #1692). This problem has been corrected. Thanks to
1096
+ Jaroslav Stika for reporting this problem.
1097
+
1098
+ * The `hasChar?` method for the
1099
+ `FXFont` class was spelled without a trailing
1100
+ question mark, but it seems more Ruby-like that it should, so we've
1101
+ added an alias for that (see RubyForge
1102
+ Bug #1714). This method also now accepts a string of size 1
1103
+ (i.e. a single character) as its input, as an alternative to an
1104
+ ordinal value. Thanks to Meinrad Recheis for these suggestions.
1105
+
1106
+ * The API documentation for the `FXImage`
1107
+ class mistakenly listed ´IMAGE_ALPHA´ as a valid
1108
+ image rendering hint, but this flag is no longer needed since FOX
1109
+ images now always contain an alpha channel (see RubyForge
1110
+ Bug #1715). The documentation has been corrected. Thanks to
1111
+ Meinrad Recheis for reporting this mistake.
1112
+
1113
+ * Due to an error in the SWIG interface files, the
1114
+ `data` method for the
1115
+ `FXSettings` class was not being wrapped
1116
+ properly. As a result, this method was unavailable and in turn led to
1117
+ other dependent methods (like `each_section`)
1118
+ to be unavailable as well (see RubyForge
1119
+ Bug #1771). This error has been corrected. Thanks to Jannis
1120
+ Pohlmann for reporting this problem.
1121
+
1122
+ * The binary gem for Windows was built with FOX version 1.2.16 and
1123
+ FXScintilla version 1.62.
1124
+
1125
+
1126
+ ## Changes For Version 1.2.5 (March 1, 2005)
1127
+
1128
+ * The change made for FXRuby version 1.2.4 regarding garbage
1129
+ collection for table items corrected only one of the problems
1130
+ described in RubyForge
1131
+ Bug #1445; There was still a problem related to the
1132
+ "destructive" effects of the `setTableSize`
1133
+ method for the `FXTable` class. This problem has
1134
+ now been corrected as well. Thanks to David Peoples, Jamey Cribbs and
1135
+ Joel VanderWerf for their assistance in helping me to track down this
1136
+ problem.
1137
+
1138
+ * The `extractText` and
1139
+ `overlayText` methods for the
1140
+ `FXTable` class were implemented incorrectly and
1141
+ weren't listed in the API documentation. These problems have been
1142
+ corrected.
1143
+
1144
+ * The checks for out-of-bounds indices in the
1145
+ `getColumnX`,
1146
+ `setColumnX`, `getRowY`,
1147
+ `setRowY` and
1148
+ `updateRange` methods for the
1149
+ `FXTable` class were incorrect. These have been
1150
+ fixed.
1151
+
1152
+ * The `setTableSize` method for the
1153
+ `FXTable` class now raises
1154
+ `ArgError` if either the number of rows or
1155
+ columns passed in as arguments is less than zero.
1156
+
1157
+ * A typo in one of the source files was causing the build to fail
1158
+ when compiled against Ruby versions 1.8.1 or earlier (see RubyForge
1159
+ Bug #1551). This error has been corrected. Thanks to Alex
1160
+ McGuire for reporting this problem.
1161
+
1162
+ * The `selectItem` method for the
1163
+ `FXTable` class was removed in FOX 1.2, so we've
1164
+ added a convenience method for this that just calls the
1165
+ `selectRange` method under the hood (see RubyForge
1166
+ Bug #1562). Thanks to Joel VanderWerf for this
1167
+ suggestion.
1168
+
1169
+ * The binary gem for Windows was built with FOX version 1.2.13 and
1170
+ FXScintilla version 1.62.
1171
+
1172
+
1173
+ ## Changes For Version 1.2.4 (February 23, 2005)
1174
+
1175
+ * Due to a change in some of the internal Ruby C APIs, a
1176
+ compile-time error for FXRuby was introduced in some of the Ruby 1.8.2
1177
+ preview releases (see RubyForge
1178
+ Bug #1039). One should not see any compile-time errors when
1179
+ compiling FXRuby (versions 1.2.3 or later) against the Ruby 1.8.2
1180
+ final release, but I've neverthless made a change to how those
1181
+ internal APIs are used, to avoid any potential problems. Thanks to the
1182
+ many users who pointed out this problem.
1183
+
1184
+ * Joel VanderWerf suggested some enhancements to the
1185
+ `image.rb` example program in order to improve its
1186
+ startup time (see RubyForge
1187
+ Bug #1281). Those changes have been incorporated. Thanks to
1188
+ Joel for this suggestion.
1189
+
1190
+ * One change for the `FXImage` class between
1191
+ FOX versions 1.0 and 1.2 is the nature of the pixel buffer that's
1192
+ passed to the `FXImage` constructor. Previously,
1193
+ this pixel buffer was expected to be a string of bytes; now it's
1194
+ expected to be an array of ´FXColor´ values. This
1195
+ modification was not implemented correctly for FXRuby versions 1.2.3
1196
+ and earlier (see RubyForge
1197
+ Bug #1427). This bug has been corrected, and the example
1198
+ program (`image.rb`) and test cases have been
1199
+ updated as well. Thanks to Oliver Smith and others for reporting this
1200
+ problem.
1201
+
1202
+ * A couple of different problems, reported by Patrick Fernie and
1203
+ David Peoples, exposed a flaw in how FXRuby manages the links between
1204
+ FOX objects and their Ruby peers when the FOX objects are destroyed
1205
+ (see RubyForge
1206
+ Bug #1445). Without going into all the gory details, let's
1207
+ just say that since we have no explicit control over when Ruby's
1208
+ garbage collector decides to "collect" those Ruby peers that point to
1209
+ C++ objects that have been destroyed, we need to take steps to
1210
+ neutralize those Ruby peer objects so that they can't cause your
1211
+ application to crash in the meantime; I've implemented a fix to take
1212
+ care of this situation. Thanks to Patrick and David for reporting
1213
+ these problems.
1214
+
1215
+ * The API documentation for FXRuby 1.2 still contained references
1216
+ to the old "spellings" of the `fxparseAccel`
1217
+ and `fxparseHotKey` method names, which were
1218
+ all lowercase (i.e. `fxparseaccel` and
1219
+ `fxparsehotkey`). (see RubyForge
1220
+ Bug #1470). These errors have been corrected.
1221
+
1222
+ * Added the `FXScrollArea#scrollCorner`
1223
+ method, which returns a reference to the scroll corner for any window
1224
+ derived from `FXScrollArea` (see RubyForge
1225
+ Feature Request #1226). Thanks to Brian Sheehan for this
1226
+ suggestion.
1227
+
1228
+ * Added the `FXMemoryBuffer#to_a` method,
1229
+ which is just an alias for the `data` accessor
1230
+ method that returns a copy of the data buffer as an array (see RubyForge
1231
+ Feature Request #1295). Thanks to Meinrad Recheis for this
1232
+ suggestion.
1233
+
1234
+ * Added the `appendRows` and
1235
+ `appendColumns` methods to the
1236
+ `FXTable` class (see RubyForge
1237
+ Feature Request #1295). Thanks to Brett Hallett for this
1238
+ suggestion.
1239
+
1240
+ * The binary gem for Windows was built with FOX version 1.2.13 and
1241
+ FXScintilla version 1.62.
1242
+
1243
+
1244
+ ## Changes For Version 1.2.3 (January 22, 2005)
1245
+
1246
+ * Since group boxes containing radio buttons no longer enforce the
1247
+ radio behavior of radio buttons (i.e. keeping only one radio button
1248
+ selected at a time), some of the example programs were no longer
1249
+ working as desired (see RubyForge
1250
+ Bug #751 and RubyForge
1251
+ Bug #1280). This problem has been corrected. Thanks to Yuri
1252
+ Leikind and Barry DeZonia for reporting this problem.
1253
+
1254
+ * Bob Sidebotham reported a little typo in the
1255
+ `table.rb` example program (see RubyForge
1256
+ Bug #990). This has been corrected.
1257
+
1258
+ * The API documentation for `FXList` did not
1259
+ reflect the changes for FOX 1.2; the
1260
+ `retrieveItem()` has been renamed to
1261
+ `getItem()` and
1262
+ `insertItem()` has been renamed to
1263
+ `setItem()` (see RubyForge
1264
+ Bug #1037 and RubyForge
1265
+ Bug #1257). This has been corrected. Thanks to Remy Drouilhet
1266
+ and Stephan Kamper for reporting this problem.
1267
+
1268
+ * The Windows installer was missing some of the documentation
1269
+ files (see RubyForge
1270
+ Bug #1139). This has been corrected. Thanks to Curt Hibbs and
1271
+ Mark Smith for reporting this problem.
1272
+
1273
+ * The `browser.rb` example program was broken
1274
+ (see RubyForge
1275
+ Bug #1146). This has been corrected. Thanks to Stefan Lang for
1276
+ reporting this problem.
1277
+
1278
+ * The attribute setter for
1279
+ `FXHeaderItem#justification` was defined
1280
+ incorrectly (see RubyForge
1281
+ Bug #1276). This has been corrected. Thanks to Joel VanderWerf
1282
+ for reporting this problem (and providing a patch to fix it).
1283
+
1284
+ * The `filenames` alias for the
1285
+ `FXFileDialog#getFilenames()` instance method
1286
+ was missing (see RubyForge
1287
+ Bug #1277). This error has been corrected. Thanks to Barry
1288
+ DeZonia for reporting this problem.
1289
+
1290
+ * The API documentation for the
1291
+ `FXFileDialog` class methods
1292
+ `getOpenFilenames()`,
1293
+ `getOpenDirectory()`,
1294
+ `getOpenFilename()` and
1295
+ `getSaveFilename()` was extremely inadequate
1296
+ (see RubyForge
1297
+ Bug #1279). This documentation has been improved. Thanks to
1298
+ Barry DeZonia for reporting this problem.
1299
+
1300
+ * Brett Hallett contributed a Ruby port of the "ratio" example
1301
+ program from the regular FOX distribution, for demonstrating the use
1302
+ of the new `FXSpring` layout manager (see RubyForge
1303
+ Bug #1282). Many thanks to Brett for this addition!
1304
+
1305
+ * Joel VanderWerf contributed code to simplify how programs
1306
+ interact with modal and non-modal dialog boxes (see RubyForge
1307
+ Bug #1283). See the API documentation for the new
1308
+ `FXDialogBox#execute_modal` and
1309
+ `FXDialogBox#execute_nonmodal` methods for
1310
+ examples of their use.
1311
+
1312
+ * The attribute setters for
1313
+ `FXRealSpinner#selBackColor` and
1314
+ `FXSpinner#selBackColor` were defined
1315
+ incorrectly (see RubyForge
1316
+ Bug #1297). These have been corrected. Thanks to Meinrad
1317
+ Recheis for reporting this problem.
1318
+
1319
+ * The `tooltipPause` attribute reader for
1320
+ the `FXApp` class was missing (see RubyForge
1321
+ Patch #1306). Thanks to Joel VanderWerf for reporting this
1322
+ omission and providing a patch to fix it.
1323
+
1324
+ * The API documentation for the
1325
+ `FXToolBarTab` class was missing (see RubyForge
1326
+ Bug #1322). Thanks to Joel VanderWerf for reporting this
1327
+ omission.
1328
+
1329
+ * The attribute accessors for
1330
+ `FXText#visibleRows` and
1331
+ `FXText#visibleColumns` were defined and
1332
+ documented incorrectly (see RubyForge
1333
+ Bug #1325). These have been corrected. Thanks to Karl El-Koura
1334
+ for reporting this problem.
1335
+
1336
+ * The binary gem for Windows was built with FOX version 1.2.13 and
1337
+ FXScintilla version 1.62.
1338
+
1339
+
1340
+ ## Changes For Version 1.2.2 (October 1, 2004)
1341
+
1342
+ * In order to avoid versioning problems when dealing with a mix of
1343
+ applications based on either FXRuby 1.0 or 1.2, the feature name for
1344
+ FXRuby has been changed from "fox" to "fox12". For most application
1345
+ developers, this means that you will need to modify the source code
1346
+ for applications targeted at FXRuby 1.2 to begin with the line
1347
+ ´require 'fox12'´Note that no
1348
+ changes should be required for legacy applications targeted at FXRuby
1349
+ 1.0.
1350
+
1351
+ * Made a number of updates to the documentation, to reflect API
1352
+ changes for FXRuby 1.2.
1353
+
1354
+ * The binary gem for Windows was built with FOX version 1.2.9 and
1355
+ FXScintilla version 1.61.
1356
+
1357
+
1358
+ ## Changes For Version 1.2a2 (July 10, 2004)
1359
+
1360
+ * This is the second "alpha" release of FXRuby 1.2. This release
1361
+ should be compatible with any FOX library version 1.2; it is not
1362
+ compatible with any previous FOX library versions. As this is an alpha
1363
+ release, users should expect a certain amount of instability, bugs,
1364
+ etc.
1365
+
1366
+ * For this release, all of the FOX 1.2 classes are available with
1367
+ the exception of the `FXBitmapView` class. There
1368
+ is a small problem with how the `FXBitmapView`
1369
+ class is declared in the FOX 1.2 header files, and I'm trying to
1370
+ decide how best to resolve that problem. The goal is to have this
1371
+ problem resolved by the next alpha release of FXRuby.
1372
+
1373
+ * For this release, all of the RDoc-based online documentation has
1374
+ been brought up to date with the new APIs.
1375
+
1376
+ * Portions of the FXRuby User's Guide were still out of date with
1377
+ respect to the new APIs (see SourceForge Bug #988623). This has been fixed.
1378
+
1379
+ * The `mditest.rb` example program was not up
1380
+ to date with the new APIs. This has been fixed.
1381
+
1382
+ * The `glviewer.rb` example program was not up
1383
+ to date with the new APIs (see SourceForge Bug #986479). This has been fixed. Thanks to Remy Drouilhet
1384
+ for reporting this problem and suggesting the fixes.
1385
+
1386
+ * The `FXGLGroup#bounds` method was defined
1387
+ incorrectly (see SourceForge Bug #986476). This has been fixed. Thanks to Remy Drouilhet
1388
+ for reporting this problem and suggesting the fix.
1389
+
1390
+ * The `scintilla-test.rb` example program was
1391
+ not up to date with the new APIs (see SourceForge Bug #986172). This has been fixed. Thanks to Peter Watkins for
1392
+ reporting this problem and submitting a corrected version of the
1393
+ program.
1394
+
1395
+ * There was a small typo in the table.rb example program (see
1396
+ SourceForge Bug #988152). This has been fixed. Thanks to Jamey Cribbs for
1397
+ reporting this problem and suggesting the fix.
1398
+
1399
+ * Due to an oversight on my part, one of the overloaded
1400
+ constructors for the `FXRegion` class wasn't
1401
+ wrapped properly (see SourceForge Bug #986181). This has been fixed. Thanks to Bil Bas for
1402
+ reporting this problem.
1403
+
1404
+ * Removed some obsolete aliases for the old leading and trailing
1405
+ rows and columns for the `FXTable` class (see
1406
+ SourceForge Bug #988038). Thanks to Yuri Leikind for reporting this
1407
+ problem.
1408
+
1409
+ * Added `FXTable` instance methods
1410
+ `horizontalGridShown=()` and
1411
+ `verticalGridShown=()` to complement the
1412
+ already available `horizontalGridShown?` and
1413
+ `verticalGridShown?` methods.
1414
+
1415
+ * The binary gem for the 1.2a1 release on Windows didn't have PNG
1416
+ or JPEG image support built-in (see SourceForge Bug #986180). This has been fixed. Thanks to Bil Bas for
1417
+ reporting this problem.
1418
+
1419
+ * The binary gem for Windows was built with FOX version 1.2.7 and
1420
+ FXScintilla version 1.61.
1421
+
1422
+
1423
+ ## Changes For Version 1.2a1 (June 28, 2004)
1424
+
1425
+ * This is the first "alpha" release of FXRuby 1.2. This release
1426
+ should be compatible with any FOX library version 1.2; it is not
1427
+ compatible with any previous FOX library versions. As this is an alpha
1428
+ release, users should expect a certain amount of instability, bugs,
1429
+ etc.
1430
+ The intent of this first alpha release is twofold. The primary
1431
+ intent is allow application developers who have current projects based
1432
+ on FXRuby 1.0 to begin the process of updating their applications for
1433
+ compatibility with FXRuby 1.2. For this release, all of the classes
1434
+ that existed in FXRuby 1.0 have been updated for compatibility with
1435
+ FOX 1.2, and so developers should at least be able to begin to "port"
1436
+ their applications forward now. Note that there have been a number of
1437
+ changes for FOX 1.2 and FXRuby 1.2, both in terms of API changes and
1438
+ less obvious "behavioral" changes. For a detailed summary of these
1439
+ changes, please see "What's New in FOX 1.2" (also available as a PDF).
1440
+ Note that few, if any, of the new classes introduced in FOX 1.2 are
1441
+ available in this first alpha release of FXRuby 1.2. Support for those
1442
+ new classes should come along quickly in subsequent alpha releases of
1443
+ FXRuby 1.2.
1444
+ The secondary intent of this first alpha release is to introduce
1445
+ the new RubyGems-based packaging
1446
+ of FXRuby and to begin to work out the inevitable kinks in that
1447
+ system.
155
1448
 
156
- === 1.6.19 / 2009-03-06
1449
+ * The binary gem for Windows was built with FOX version 1.2.4 and
1450
+ FXScintilla version 1.57.
157
1451
 
158
- * Please see http://www.fxruby.org/doc/changes.html
159
- for a complete list of the changes in this release.