[fxruby-users] Re: FXRuby issues
sander at knology.net
Sat Sep 3 09:39:31 EDT 2005
On Saturday 03 September 2005 10:15 am, Lyle Johnson wrote:
> On Sep 3, 2005, at 3:58 AM, Gonzalo Garramuno wrote:
> > Sorry to bother you personally, but after working with FXRuby for the
> > first time on a relatively medium-sized project, I collected a list of
> > things that seem to be broken in fxruby (or fox), and I thought it
> > would be good for you guys to be aware of.
> > Some of these things I consider them somewhat serious in term of
> > recommending fxruby for larger projects, which is unfortunate, cause I
> > overally really liked how the API is designed.
> > Unless specified, problems seem to show in both 1.2 and 1.4, under
> > Windows, at least. The main things I run into problems were:
> > * Segfaults.
> > FXRuby segfaults quite a lot. This, for once, happens when things are
> > not created, which is understandable, but bad anyway, compared to
> > other toolkits like FLTK, TK, etc. where segfaults are simply not
> > possible (other than the library is buggy).
> When an FXRuby application segfaults, it's almost always the fault of
> the FXRuby bindings themselves and not the underlying FOX library.
> > But more so, I also found segfaults with:
> > - crashes when creating large canvases/images. These were pretty
> > weird. I basically could not get FxRuby to have a 4K or
> > 8K canvas+image buffer.
Well there are GDI limits ofcourse.... FOX will throw a exception if limits
More information about the fxruby-users