From: Marius Vollmer <mvo@zagadka.ping.de>
To: Daniel Skarda <0rfelyus@ucw.cz>
Cc: guile-gtk <guile-gtk@sources.redhat.com>
Subject: Re: implementing guile-gtk drag & drop...
Date: Sun, 10 Nov 2002 12:57:00 -0000 [thread overview]
Message-ID: <87k7jlf8gl.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m065v5fb3s.fsf@hobitin.ucw.cz>
Daniel Skarda <0rfelyus@ucw.cz> writes:
> > Using gtk_selection_data_copy/free seems to be the right thing to do.
> > Can you figure out why they made drag and drop fail? Maybe there are
> > bugs in those functions that we can work around.
>
> Unfortunately Gtk creates GtkSelectionData, invokes a handler and
> expects that you gtk_selection_data_set on data that Gtk passed to
> handler, not to its copy :-( See gtkselection.c.
Aha. So gtk_selection_data_copy is useless and GtkSelectionData
should really be using reference counting, right?
In that case, we need a new kind of life-time management option in
guile-gtk: the Scheme value that represents a GtkSelectionData needs
to be invalidated when the real GtkSelectionData is freed.
We don't have such a mechanism currently, but it should not be that
difficult to add it. Basically, sgtk_callback_marshal would need to
'destroy' the arguments of the callback when it has returned.
Any takers?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
prev parent reply other threads:[~2002-11-10 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 3:49 Stanislas Pinte
2002-11-03 7:03 ` Marius Vollmer
2002-11-05 16:20 ` Daniel Skarda
2002-11-06 0:58 ` Stan Pinte
2002-11-06 5:17 ` Daniel Skarda
2002-11-06 5:26 ` Stan Pinte
2002-11-09 10:56 ` Marius Vollmer
2002-11-10 12:20 ` Daniel Skarda
2002-11-10 12:57 ` Marius Vollmer [this message]
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=87k7jlf8gl.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=0rfelyus@ucw.cz \
--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).