From: Stan Pinte <alto_stan@wanadoo.be>
To: Daniel Skarda <0rfelyus@ucw.cz>,Marius Vollmer <mvo@zagadka.ping.de>
Cc: Stanislas Pinte <alto_stan@wanadoo.be>,
guile-gtk <guile-gtk@sources.redhat.com>,David Pirotte
<david@altosw.be>
Subject: Re: implementing guile-gtk drag & drop...
Date: Wed, 06 Nov 2002 00:58:00 -0000 [thread overview]
Message-ID: <5.1.1.6.0.20021106094931.00a91210@pop.wanadoo.be> (raw)
In-Reply-To: <m0iszbmtlb.fsf@hobitin.ucw.cz>
At 01:26 6-11-2002 +0100, Daniel Skarda wrote:
>Hello,
>
> last few hours I played with guile-gtk and drag'n'drop and I wrote bindings
>for dnd functions. I was able to to write working scheme sibling of testdnd.c.
>
> The biggest problem was GtkSelectionData - a Gtk structure without
> "classic"
>reference counting,
do you know where I can find a good explanation of the reference counting
strategies, in GTK?
Because I don't understand what is the problem...(blame my very poor
knowledge of guile-gtk and gtk)
thanks,
Stan.
>moreover it is parameter of many gtk callbacks and dnd
>stopped working when I use gtk_selection_data_copy/free :-(
>
> My (temporal) solution is little bit unsafe - or it is save until you copy
>signal-data outside of signal handler and use it later. I guess this is very
>unlikely but guile-gtk should be adjusted to handle such wild code
>(unfortunately, this GtkSelectionData "feature" was not improved in Gtk+
>2.0 :-(
>
> I post my patch once I clean up my code.
>
>0.
next prev parent reply other threads:[~2002-11-06 8:58 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 [this message]
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
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=5.1.1.6.0.20021106094931.00a91210@pop.wanadoo.be \
--to=alto_stan@wanadoo.be \
--cc=0rfelyus@ucw.cz \
--cc=david@altosw.be \
--cc=guile-gtk@sources.redhat.com \
--cc=mvo@zagadka.ping.de \
/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).