These have been added. A change made in Ruby 1. Thanks to a change in FOX version 1. These problems have been fixed. A few problems were discovered for the inputs. Several instance methods for the FXTable class were not actually present under their documented names see RubyForge Bug The build script was not compatible with changes made in the recently-released FXScintilla 1.
Now it does. The binary gem for Windows was built with FOX version 1. The dilbert. The code related to the localization of application messages in FOX wasn't implemented properly in FXRuby, and as a result, constructing certain dialogs like the color dialog could cause a program to crash see RubyForge Bug The "Stop Spin" button in the gltest. This was actually a symptom of a larger problem, that FXRuby wasn't properly handling timers and chores. The textedit. This example has been updated.
The new font method for the FXFont class was not documented. As discussed in various forums see for example this post , the autorequire directive for RubyGems specifications is now deprecated. As a result, this has been removed from the FXRuby gem specification. One of the most signficant changes for FOX 1.
For a comprehensive overview of the changes made to FOX since version 1. Added the allowSide , disallowSide and allowedSide? The browser. This error has been corrected. Thanks to Javier Goizueta for initially reporting this problem, and especially to Tobias Peters for providing a patch. Thanks to Manfred Usselmann for reporting this problem. Thanks to Gerard Menochet for reporting this problem. Thanks to Uwe Hartl for reporting this problem. Thanks to Meinrad Recheis Henon for reporting this problem.
Along the same lines, the message data for those widgets wasn't being converted correctly see RubyForge Bug Both of these errors have been corrected. Thanks to Meinrad Recheis Henon for reporting these problems. Thanks to Joel VanderWerf for reporting this problem. The FXTableItem constructor was supposed to optionally accept a reference to an arbitrary Ruby object as its third argument, but this wasn't working properly see RubyForge Bug Thanks to Mark Volkman for reporting this problem.
The build instructions for Unix platforms had not been updated recently and as such contained some errors see RubyForge Bug These errors have been corrected. Thanks to Dave Burns for reporting this problem. The extendSelection method for the FXTable class was raising an exception if an out of bounds row or column index was passed in see RubyForge Bug This has been changed so that extendSelection instead returns false for out of bounds arguments.
Thanks to Leonid Moiseichuk for reporting this problem. Thanks to Liam Irish for reporting this problem and providing a patch. All of these problems have been corrected. This oversight has been corrected. Thanks to Tim Smith for reporting this problem. The scintilla. Thanks to Maxim Kulkin for reporting this problem. Due to changes in the APIs for timers and chores, the mechanisms for removing chores and timeouts were broken see RubyForge Bug Thanks to "moinker" for reporting this problem.
Thanks to Peter for reporting this problem. Due to a bug in the test suite runner script, not all test cases were being exercised see RubyForge Bug Calling the getPixel method for the FXImage class when the client-side pixel buffer for the image has already been released would cause a program to crash see RubyForge Bug Now, getPixel will raise an exception if it's called after the pixel buffer has been released.
The documentation for getPixel has been updated accordingly. Thanks to Gonzalo Garramuno for reporting this problem. The makePositionVisible method for the FXTable class was raising an exception when passed out-of-bounds values for the row or column index see RubyForge Bug This could happen, for example, if you were to click in a table area outside of the regular cells which indirectly triggers a call to makePositionVisible.
This was actually inconsistent with standard FOX behavior, which simply ignores out of bounds values for that method's arguments. This bug has been fixed, and the documentation for makePositionVisible has been updated accordingly. Thanks to Ralf Jonas for reporting this problem. Due to a bug in the implementation, the checked? Thanks to Meinrad Recheis for reporting this problem.
Those errors have been corrected. Thanks to Pavel Sokolov for reporting these problems. There were a number of bugs in the textedit.
Thanks to Claude Marinier for reporting these problems. Thanks to Bill Atkins for reporting this problem. Thanks to Jacob Hansen for reporting this problem. For a history of the changes made during the FOX 1. The iconlist. This pulldown menu has been removed from that example. The checked? Thanks to Oliver Smith for reporting this problem. Thanks to Jannis Pohlmann for reporting this mistake. Some code in the groupbox.
Thanks to Jaroslav Stika for reporting this problem. The hasChar? This method also now accepts a string of size 1 i. Thanks to Meinrad Recheis for these suggestions. Thanks to Meinrad Recheis for reporting this mistake. Thanks to Jannis Pohlmann for reporting this problem. The change made for FXRuby version 1. Rubinius Terminal is heavily inspired by term2, term, and terminal. Thanks to the authors of those packages.
The term. The copyright notice for term. Good catch. Asked 7 years, 8 months ago. Active 7 years, 8 months ago. Viewed times. Here is the error: Using worker: worker-linux Checking connectivity Searching for binary rubies, this might take some time. Requested binary installation but no rubies are available to download, consider skipping --binary flag. Gemset '' does not exist, 'rvm rbx do rvm gemset create ' first, or append '--create'. The command "rvm use rbx --install --binary --fuzzy" failed and exited with 2 during setup.
Your build has been stopped. Here is my. Improve this question. Max Max
0コメント