Activity (RSS)

Merged with https://github.com/larskanis/fxruby/commit/94b0663c220952b281103271... .

This is solved in 1.6.22.

This is solved in 1.6.22.

This is solved in 1.6.22.

This happens also under Debian Squeeze running ruby 1.9.2-p180 and fxruby-1.6.20.

It seems that the destruction of the application is not working correctly, bec...

(from [ed6af26685a586605164161d5aeb4c0c4d907ecc]) Modified the generate_kwargs_lib.rb script so that it remembers the previous warning level the user had set in...

The documentation for FXTopWindow needs to be corrected to reflect the fact that you only get SEL_MINIMIZE, SEL_MAXIMIZE, SEL_RESTORE and SEL_CLOSE when you cal...

FXImage.rotate results in a segmentation fault if the rotation is used for other than 0, 90, 180 or 270 degrees. The Fox toolkit only supports these degrees for...

Tim, I can't reproduce this bug on Windows XP, using Ruby 1.8.6 (2007-09-24 patchlevel 111) and FXRuby 1.6.16, if I remove the call to exit at the end of the ch...

I've tested it with the latest (post-1.6.16) FXRuby code and while it still crashes if you exit immediately after creating the table item, it doesn't crash if y...

The following code crashes on exit on XP and Vista with Ruby 1.8.6 and FXRuby 1.6.16. The crash remains if setItemJustify is replaced with setItemBorders, but n...

I didn't even realize that Ruby defined those constants. Ugh. Yes, we ought to see if we can get rid of those in FXRuby 1.8. I don't want to make that kind of A...

After "require 'fox16'" we have:

Fox::TRUE -> 1
Fox::FALSE -> 0
Fox::MAYBE -> 2

Meanwhile, Ruby has built-in constants:

TRUE -> true
FALSE -> false

So after "in...

OP replied:

This is just an example. The actual code has since been rewritten to use app.addTimeout with :repeat = true in place of the thread, and in fact I'm ...

Lyle asked the OP:

Tim, what is it that you're trying to accomplish in this code (or in the actual code, if this is just an example)? Since all of the GUI stuff...

In the following code, any of FXMessageBox.error, FXMessageBox.information, FXMessageBox.question, and FXMessageBox.warning will cause a seg-fault (WinXP, Ruby ...

Originally submitted by Tim Hunter:

One of FXTableItem.drawContent's parameters is a device context dc. This parameter seems to be unusable - calls to dc.drawTe...

Added checks for passing nil to FXMainWindow.new() and FXDialogBox.new() in FXRuby 1.6.15. Tim noted the problem still exists for many other classes (e.g. FXBut...

FXRuby seg-faults when nil is passed as the first parameter to various constructors: e.g. FXMainWindow.new(nil, ''), FXDialogBox.new(nil, ''). These cases shoul...

User Jim Hall added:

I'm getting the same behavior on windows even when testing using a dummy IO object directly:

dumsocket=IO.new(0,"r")
@application.addInput...

Lyle replied: I have the feeling this doesn't work for sockets (as you suspected). The way in which Ruby abstracts files and sockets as general-purpose I/O obje...

On Windows, when creating a TCPServer socket and calling addInput, i.e.

@srvSock = TCPServer.new("127.0.0.1", 7777)
addInput(srvSock, INPUT_READ, method(:gotCn...

A workaround would be to set the DEF_MOVE_CURSOR back to nil in your program's exit handler. The problem is that FOX is trying to double-delete the same cursor ...

A user was attempting to change the DEF_MOVE_CURSOR. This code worked:

FXApp.new do |app|
  app.setDefaultCursor(DEF_MOVE_CURSOR, FXCursor.new(app))
  ...
end

Using setHotX() and setHotY() after the cursor has been created have no effect (by design). Need to come up with an example to confirm that hotspot values in th...

As reported by Gonzalo Garramuno to the mailing list:

Custom mouse icons will not allow hotspot to be changed. Setting hotspot to anything positive in the const...

This appears to be missing for FXIconList, and I suspect it's missing for the other classes too. Need to see what it will take to get this working.

As submitted by Joel VanderWerf:

I had to convert some modal dialogs to non-modal, and I abstracted out some of what I was doing. The result is a mixin that use...

This is just a placeholder in case any one else notices this problem. Postponing a SWIG update until 1.8.0.

An improved version that includes more realistic physics (?).

The FXTextField#editable and FXWindow#each_child_recursive methods were added in 1.6.11. Still considering FXTable#deselectRange.

These are some standard extensions that I usually throw in when I am using FXRuby. (They are in FoxTails actually.)

What do you think about adopting them into F...

The gem rdoc output is much better than before (Thanks!) but there's still one small problem: the FXWindow page doesn't show correct parent (it shows Object, no...

An improved version of the Scribble example that remembers the lines that have been drawn, so that it can redraw itself after an expose.

(from [ed77236fb21adf17187b86e9f81e29da9c45d770]) Modified the generate_kwargs_lib.rb script so that it remembers the previous warning level the user had set in...