Re: texinfo documentation

[Marko Rauhamaa <marko at pacujo dot net>]

Kevin Ryde <user42@zip.com.au>:

> I think the function called gdk-gc-set-clip-rectangle should be the
> same as the corresponding C function.

I have now changed all the rectangle-inputting procedures to input
GdkRectangle's instead of (x,y,w,h).

> By all means add some extra routine if the basic way is too painful,
> but I think variations between C and scheme functions (of the same
> name) will only serve to cause confusion.

Here are examples of the few remaining discrepancies:

 - C: gboolean gdk_rectangle_intersect (GdkRectangle *r1,
                                        GdkRectangle *r2,
                                        GdkRectangle *dest);

   guile-gtk: (gdk-rectangle-intersect rect1 rect2) => rect or #f

   instead of: (gdk-rectangle-intersect rect1 rect2) => (bool rect)

 - C: void gdk_rectangle_union (GdkRectangle *src1,
                                GdkRectangle *src2,
                                GdkRectangle *dest);

   guile-gtk: (gdk-rectangle-union rect1 rect2) => rect

   instead of: (gdk-rectangle-union rect1 rect2) => (rect)

 - C: gint gdk_string_to_compound_text (const gchar *str,
					GdkAtom *encoding, gint *format,
					guchar **ctext, gint *length);

   (where the return value is 0 on success)

   guile-gtk: (gdk-string-to-compound str) => (string or #f
                                               encoding
                                               format)

   instead of: (gdk-string-to-compound str) => (int
                                                encoding
                                                format
                                                (cvecr uint))


Marko

-- 
Marko Rauhamaa      mailto:marko@pacujo.net     http://pacujo.net/marko/