public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: guile-gtk@sources.redhat.com
Subject: gdk-window-get-origin (was: texinfo documentation)
Date: Mon, 02 Jun 2003 23:51:00 -0000	[thread overview]
Message-ID: <87wug4f3qa.fsf_-_@zip.com.au> (raw)
In-Reply-To: <m3n0h25svu.fsf@lumo.pacujo.net> (Marko Rauhamaa's message of "31 May 2003 21:22:29 -0700")

Marko Rauhamaa <marko@pacujo.net> writes:
>
>    gdk-window-get-origin
>
> was written prior to my time, and it returns (x . y)

There are a few such.  gdk-window-get-size was the only one I'd been
using.  I'm going to put the following in the docs.

 - Function: gdk-window-get-deskrelative-origin window
 - Function: gdk-window-get-origin window
 - Function: gdk-window-get-position window
 - Function: gdk-window-get-root-origin window
 - Function: gdk-window-get-size window
     Unlike other multiple-return values functions, these return a pair
     rather than a list.  The `car' is X and the `cdr' is Y.  Or for
     `gdk-window-get-size' the same for WIDTH and HEIGHT.

> That precedent led to a whole slew of other analogous GdkPoint routines,
> and it was only natural to extend the principle to GdkRectangle as well.

I think the above should be regarded as unfortunate departures from
the multiple-values convention.

> While I could back out on my changes,

Please do so.

> this one would require a higher
> authority. Now, gdk-window-get-origin is not included in my SuSE 7.3
> release (guile-gtk ver. 0.19). Was it ever released out to the public?
> It is a vintage function according to the ChangeLog (2001-02-04).

They look to me too long established to be changed.

> Each guile-gtk function signature needs to be mentioned.

The aim, I think, is still that this should not be necessary.  Careful
attention to uniformity should keep exceptions to a minimum.

Even if it does turn out to be worth having each described, it's still
got to be highly desirable to have maximum consistency with the
corresponding C functions.

  reply	other threads:[~2003-06-02 23:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12  1:21 texinfo documentation Kevin Ryde
2003-05-12  1:52 ` Marko Rauhamaa
2003-05-23 22:01   ` Kevin Ryde
2003-05-23 23:36     ` Marko Rauhamaa
2003-05-23 23:57       ` Kevin Ryde
2003-05-24  0:05         ` Marko Rauhamaa
2003-05-24  2:19           ` Kevin Ryde
     [not found]             ` <m3llwwdhjf.fsf@lumo.pacujo.net>
2003-05-25 22:48               ` Kevin Ryde
2003-05-25 23:28                 ` Marko Rauhamaa
2003-05-26  0:06                   ` Kevin Ryde
2003-05-26  2:42                     ` Marko Rauhamaa
2003-05-29 23:37                       ` Kevin Ryde
2003-05-30  1:06                         ` Marko Rauhamaa
2003-06-13 22:05                           ` gdk-string-to-compound (was: texinfo documentation) Kevin Ryde
2003-07-07 22:30                             ` gdk-string-to-compound Kevin Ryde
2003-05-29 23:43                       ` texinfo documentation Kevin Ryde
2003-06-01  4:31                         ` Marko Rauhamaa
2003-06-02 23:51                           ` Kevin Ryde [this message]
2003-07-07 22:29                         ` gdk-window-get-geometry (was: texinfo documentation) Kevin Ryde
2003-05-26  0:07                   ` gdk-rectangle-new " Kevin Ryde
2003-05-26  1:20                     ` Marko Rauhamaa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wug4f3qa.fsf_-_@zip.com.au \
    --to=user42@zip.com.au \
    --cc=guile-gtk@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).