From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: menu loop (patch)
Date: Sat, 19 Jul 2008 21:52:51 +0200 [thread overview]
Message-ID: <20080719195251.GA10533@thorin> (raw)
In-Reply-To: <20080719172134.GA3760@pina.cat>
On Sat, Jul 19, 2008 at 07:21:34PM +0200, Carles Pina i Estany wrote:
> > I'm not sure if this is intentional. Size is not important in this
> > part of the code, but in other UI menus (e.g. Iceweasel or GNOME) I
>
> fast check in KDE: it's looping
>
> Also, Iceweasel menus are looping here (maybe because it's executed
> in KDE and there is some GTK Widget with a different behaviour? I have
> no idea)
I think it depends on the type of menu. Iceweasel's stored password list
doesn't loop, but pull-down menus do. I'm not sure if there's a rationale
for this..
> > notice this is not done. It could also be a nuissance for users who
> > want to go rapidly to the top or bottom (sure, they can use PgUp/PgDn,
> > but then aren't we making the behaviour of those keys inconsistent
> > with arrows?).
>
> I would be glad to add some functionality for PgUp/PgDown and also for
> Home/End keys (I would do it today evening or tomorrow and send the
> patch).
Actually, I just noticed we don't handle any of these. Don't worry about
that.
> > Also, if you (or anyone) can point to a "usability best practices"
> > reference saying this has been carefuly analized and one of the
> > options was found to be better, I think this would help us make a
> > decision.
>
> I will also check tonight.
Good!
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-07-19 19:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 21:22 menu loop (patch) Carles Pina i Estany
2008-07-19 15:40 ` Robert Millan
2008-07-19 17:21 ` Carles Pina i Estany
2008-07-19 19:52 ` Robert Millan [this message]
2008-07-19 22:12 ` Carles Pina i Estany
2008-07-19 23:26 ` Isaac Dupree
2008-07-19 23:31 ` Carles Pina i Estany
2008-07-19 23:45 ` Isaac Dupree
2008-07-20 4:24 ` Colin D Bennett
2008-07-19 17:34 ` Colin D Bennett
2008-07-19 19:58 ` Robert Millan
2008-07-19 20:31 ` Yoshinori K. Okuji
2008-07-19 22:06 ` Carles Pina i Estany
2008-07-19 22:15 ` Robert Millan
2008-07-19 22:28 ` Colin D Bennett
-- strict thread matches above, loose matches on Subject: below --
2008-07-20 6:21 chaac
2008-07-20 8:49 ` Carles Pina i Estany
2008-07-22 21:40 ` Robert Millan
2008-08-05 7:15 ` Vesa Jääskeläinen
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=20080719195251.GA10533@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/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