Re: Bug#246846: Is this bug still present in lablgtk2 2.4.0+2005.02.18-1 ?

[Sven Luther <sven.luther@wanadoo.fr>]

On Sun, May 08, 2005 at 06:43:00PM +0900, Jacques Garrigue wrote:
> From: Sven Luther <sven.luther@wanadoo.fr>
> > On Sat, May 07, 2005 at 08:25:48PM +0200, Julien PUYDT wrote:
> > > Sven Luther a écrit :
> > > >Hello,
> > > >
> > > >I would like to know if this bug was still present in the current version 
> > > >of
> > > >lablgtk2 in sarge ? 
> > > 
> > > I don't know if it's the release in sarge, but I just rechecked the ones 
> > > I pointed as problematic with the current lablgtk2 in unstable, and on 
> > > those the result is:
> > 
> > Thanks for testing and your fast reply.
> > 
> > > * csview.ml:
> > > File "csview.ml", line 51, characters 4-6:
> > > Syntax error
> 
> csview.ml uses stream parsers, which are provided by camlp4.
> There is now a comment in the file:
> (* Compile with
>      ocamlc -pp camlp4o -I +lablgtk2 lablgtk.cma csview.ml -o csview
>    or run with
>      lablgtk2 camlp4o.cma csview.ml <file.csv>
> *)

Ok. Maybe having a Makefile in the examples which would launch the individual
examples would be a good idea.

> > > * events.ml:
> > > doesn't crash but gives things like:
> > > (ocaml:7938): Gtk-CRITICAL **: gtk_text_view_start_selection_drag: 
> > > assertion `text_view->selection_drag_handler == 0' failed
> 
> events.ml is old code, which was an attempt to get the cursor position
> using the old text widget. This was always buggy. Fortunately, the new
> text widget causes no such problem (events2.ml).

What about moving old examples to a lablgtk1 or old or whatever directory ?

> > > * tictactoe.ml:
> > > File "tictactoe.ml", line 30, characters 26-48:
> > > Unbound value GtkNew.make_new_widget
> 
> GtkNew is not ported. This was never clear how useful it would be to
> implement it on the ML side.
> Should remove this test for the time being.

Ok.

> > > * text/test_text.ml:
> > > File "text/test_text.ml", line 74, characters 11-25:
> > > Unbound value GText.tagtable
> 
> Oops. API changes. I've just fixed it in CVS.

Thanks. Any new CVS-snapshot release in sight ?

> Thanks for all these reports.

No problem, thank Julien for it, he is the one who found them out.

Friendly,

Sven Luther