On Mon, Oct 20, 2008 at 05:19:03PM +0200, Thomas Orgis wrote:
Am Mon, 20 Oct 2008 16:59:34 +0200 schrieb Johannes Hofmann <Johannes.Hofmann@gmx.de>:
With these options I can reproduce the problem. I guess --enable-cairo is the problematic one. Can you try to compile dillo with a manually compiled fltk2 without --enable-cairo?
Nothing easier than that with the source-based distro;-)
Yes, that's nice. I use pkgsrc;-)
I have a system fltk2 lib now without cairo and now dillo2 works nicely! So cairo in FLTK2 is buggy? Or its usage in dillo... but I suppose that FLTK2 should abstract that away.
Not sure, but given the fact that cairo support is switched off by default, I guess it's just not stable enough yet.
This could meant that we can close the bug; but the information about the cairo issue should be FAQed somewhere -- ideally, of course, solved upstream.
Yes, we should mention that somewhere. FAQ or README?
Btw: FLTK2 not having a stable release is a bit of a problem with replacing the old "stable" dillo with dillo2... I hope that situation is resolved soon. Well, and the missing feature of frames; whatever one's opinion, the dillo patch that enabled this is commonplace and this missing is a de facto regression...
Nobody would be opposed to a clean patch that implements frames I think. Cheers, Johannes