From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Add an ellipsis to the preferences menu item
Date: Fri, 26 Oct 2007 01:29:39 +0100 [thread overview]
Message-ID: <1193358579.25405.158.camel@cookie.hadess.net> (raw)
In-Reply-To: <1193352257.6184.282.camel@violet>
On Fri, 2007-10-26 at 00:44 +0200, Marcel Holtmann wrote:
> Hi Chris,
>
> > Since the Preferences menu entry in the applet opens a new window it
> > should probably have an ellipsis in the label. Attached is a trivial
> > patch to add this.
>
> what does the HIG recommend for applet menus. I wanna follow the HIG.
> Currently I simply did what all other applets do that I have running.
This one is a toss-up between what's right, and what GTK+ implements. It
doesn't have separate strings for menus, so you don't get the ellipsis.
I'm sure there's a GTK+ bug opened somewhere about "doing the right
thing" in the case of stock items.
So it's really up to you. Personally, I'd stick with the stock item,
unless you have a wide-ranging amount of translations (which you'd get
if you moved bluez-gnome to GNOME SVN, hint hint :)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-26 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 19:20 [Bluez-devel] [PATCH] Add an ellipsis to the preferences menu item Chris Rivera
2007-10-25 22:44 ` Marcel Holtmann
2007-10-25 23:22 ` Chris Rivera
2007-10-26 0:29 ` Bastien Nocera [this message]
2007-10-31 16:33 ` 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=1193358579.25405.158.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--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