From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Beautify about dialog
Date: Sun, 16 Dec 2007 22:47:30 +0100 [thread overview]
Message-ID: <1197841650.8050.39.camel@aeonflux> (raw)
In-Reply-To: <8a8adccc0712161309m29c70a45x212bead7a823d808@mail.gmail.com>
Hi Jaap,
> Attached patch does the following
>
> * about dialog code is simpler
you can't use gtk_dialog_run for the applet's about dialog. It will
block and thus block all PIN requests. The current code is this way for
a reason.
> * email address and URLs are clickable
Send a separate patch for this.
> * Makes sure that every window gets a bluetooth window icon
This should be already working. And if it is missing somewhere, I need a
separate patch for it.
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-12-16 21:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 21:09 [Bluez-devel] [PATCH] Beautify about dialog Jaap A. Haitsma
2007-12-16 21:47 ` Marcel Holtmann [this message]
2007-12-16 22:43 ` Jaap A. Haitsma
2007-12-16 23:24 ` Bastien Nocera
2007-12-17 1:03 ` Marcel Holtmann
2007-12-17 7:15 ` Jaap A. Haitsma
2007-12-17 7:54 ` Jaap A. Haitsma
2007-12-17 10:43 ` Bastien Nocera
2007-12-17 19:04 ` Marcel Holtmann
2007-12-18 21:52 ` Jaap A. Haitsma
2007-12-18 23:22 ` Marcel Holtmann
2007-12-20 22:24 ` Jaap A. Haitsma
2007-12-17 0:58 ` Marcel Holtmann
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=1197841650.8050.39.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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