From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Christian Franke <Christian.Franke@t-online.de>
Subject: Re: [PATCH setup] Add tooltip for Ctrl+I/R/U accelerator keys
Date: Thu, 2 Feb 2023 16:05:32 +0000 [thread overview]
Message-ID: <a3d54569-4ab0-1c29-c681-fce44fa60e8b@dronecode.org.uk> (raw)
In-Reply-To: <3f2e6d0f-100d-bf00-4f7f-839bc64b26fc@t-online.de>
On 22/11/2022 16:00, Christian Franke wrote:
> This is a first try to make these keys more obvious as requested on the
> Cygwin ML.
>
> A more complex approach would be to mention only the keys which actually
> would change the current package state.
Thanks for this patch.
So, I appreciate what this is trying to do, but I have great difficultly
convincing myself that this is the right approach.
We don't need to resort to a tooltip for any other shortcut, because
there is an established visual design language to indicate those. I
guess we just need to find what's consistent with pre-existing ways of
indicating this kind of behaviour in other applications.
next prev parent reply other threads:[~2023-02-02 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 16:00 Christian Franke
2023-02-02 16:05 ` Jon Turney [this message]
2023-02-02 17:48 ` Christian Franke
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=a3d54569-4ab0-1c29-c681-fce44fa60e8b@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Christian.Franke@t-online.de \
--cc=cygwin-apps@cygwin.com \
/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).