public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
To: Stephen Tell <tell@cs.unc.edu>
Cc: Guile-Gtk List <guile-gtk@sourceware.cygnus.com>
Subject: Re: Converting GdkEvent from C to Guile
Date: Thu, 18 Nov 1999 15:14:00 -0000	[thread overview]
Message-ID: <87iu2ze792.fsf@zagadka.ping.de> (raw)
In-Reply-To: <Pine.GHP.4.10.9911181556440.27875-100000@rukbat.cs.unc.edu>

Stephen Tell <tell@cs.unc.edu> writes:

> In guile-gtk 0.17, how do I convert a pointer to a GdkEvent (or
> GdkEventButton) to an SCM so it can be passed to a guile callback?

You use

    GdkEvent *ev;
    SCM val;

    extern sgtk_boxed_info sgtk_gdk_event_info;
    val = sgtk_boxed2scm (ev, &sgtk_gdk_event_info, copyp);

COPYP determines whether sgtk_boxed2scm will amke a copy of EV or not.
If you want guile-gtk to become owner of the GdkEvent structure
pointed to by EV (i.e guile-gtk can free it whenever it likes, using
gdk_event_free) you would use FALSE for COPYP.  When you want to stay
the owner of EV, say TRUE.  You should only say FALSE when EV is the
result of gdk_event_copy, as a rule.
 
- Marius

-- 
(let ((p #(78 91 29 77 90 51 71 91 86 24 54 55 119 16 104 62 42 58 121 80 10
124 48 102 79 22 12 116 27 34 37 100 16 83 115 40 126)))  (define (x n)  (do
((i 0 (1+ i))  (s 0 (+ s (* (vector-ref p i)  (expt n i)))))  ((= i 37) s)))
(do ((i 1 (1+ i))) ((= i 38)) (display (integer->char (modulo (x i) 127)))))

  reply	other threads:[~1999-11-18 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-07 15:47 guile-gtk without dlopen (HP-UX) Stephen Tell
1999-11-08 13:27 ` Marius Vollmer
1999-11-08 19:08   ` Stephen Tell
1999-11-18 13:05 ` Converting GdkEvent from C to Guile Stephen Tell
1999-11-18 15:14   ` Marius Vollmer [this message]
1999-11-18 15:50     ` Stephen Tell
1999-11-19 13:51       ` Marius Vollmer

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=87iu2ze792.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=tell@cs.unc.edu \
    /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).