From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [patch] Use buttons in notification popups
Date: Mon, 03 Dec 2007 17:26:52 +0100 [thread overview]
Message-ID: <1196699212.12292.115.camel@violet> (raw)
In-Reply-To: <1196677470.3227.192.camel@cookie.hadess.net>
Hi Bastien,
> As reported here:
> https://bugzilla.redhat.com/show_bug.cgi?id=407551
>
> notification-daemon kind of sucks and doesn't allow for long messages
> (it will clip the messages, see those screenshots:
> https://bugzilla.redhat.com/attachment.cgi?id=274901
> https://bugzilla.redhat.com/attachment.cgi?id=274911
> )
>
> Attached patch removes the extra lines, and adds a button to the popup
> instead. It looks better, and still pops up the dialogues as expected.
look good to me. Any special requirements on the version of libnotify to
make this work?
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
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-03 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 10:24 [Bluez-devel] [patch] Use buttons in notification popups Bastien Nocera
2007-12-03 16:26 ` Marcel Holtmann [this message]
2007-12-03 16:32 ` Bastien Nocera
2007-12-03 17:04 ` Marcel Holtmann
2007-12-04 14:03 ` Bastien Nocera
2007-12-04 15:31 ` 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=1196699212.12292.115.camel@violet \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.