public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Christian Franke <Christian.Franke@t-online.de>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH setup] Keyboard accelerators for install/reinstall/uninstall
Date: Tue, 23 Aug 2022 16:16:52 +0100	[thread overview]
Message-ID: <cca37e6e-2db2-79eb-47d5-d094c586c2ed@dronecode.org.uk> (raw)
In-Reply-To: <3b69d761-018e-dbc3-db57-369f6bf057bb@t-online.de>

On 22/08/2022 16:29, Christian Franke wrote:
> Jon Turney wrote:
>> On 14/08/2022 12:57, Christian Franke wrote:
>>> This eases state changes of a selected sequence of packages.
>>
>> Nice!  The keyboard control of the package chooser was a bit of an 
>> after-thought, which it really shouldn't be.
> 
> Thanks - revised patch is attached.
> 

Thanks.  This looks good.  Please apply.

>>> Ctrl+U is in particular useful to cleanup installations in 
>>> conjunction with "unneeded" view:
>>> https://sourceware.org/pipermail/cygwin-apps/2022-August/042185.html
>>>
>>> Open issue: Add some visual clue (tooltip?) to make this 
>>> functionality more obvious.
>>
>> Yeah.  These shortcuts should also be accelerators for the package 
>> action selection popup menu, which would make them more discoverable?
> 
> Handling these in the popup menu is possibly tricky. According to 
> documentation of TrackPopupMenu(), hWndListView "receives all messages 
> from the menu" which is apparently not the case.

Confused. I don't think that matters (we could probably be using 
TPM_NONOTIFY), because we use TPM_RETURNCMD.

If we mark accelerators in the menu:

--- a/res/en/res.rc
+++ b/res/en/res.rc
@@ -573,11 +573,11 @@ BEGIN
      IDS_PROGRESS_POSTINSTALL "Running..."
      IDS_PROGRESS_SOLVING "Solving dependencies..."
      IDS_ACTION_DEFAULT "Default"
-    IDS_ACTION_INSTALL "Install"
-    IDS_ACTION_UNINSTALL "Uninstall"
+    IDS_ACTION_INSTALL "&Install"
+    IDS_ACTION_UNINSTALL "&Uninstall"
      IDS_ACTION_SKIP "Skip"
      IDS_ACTION_KEEP "Keep"
-    IDS_ACTION_REINSTALL "Reinstall"
+    IDS_ACTION_REINSTALL "&Reinstall"
      IDS_ACTION_RETRIEVE "Retrieve"
      IDS_ACTION_UNKNOWN "Unknown"
      IDS_ACTION_SOURCE "Source"

They appear when the menu is opened by pressing the menu key (or always, 
if "Underline access keys when available" is on in ease-of-access 
settings), and menu items can be chosen using them.

It's not quite that straightforward because we need to remove the '&' 
when those strings are used elsewhere (e.g. in the action column), but I 
think it can be done...

>>> @@ -670,6 +670,10 @@ packagemeta::set_action (_actions action, 
>>> packageversion const &default_version,
>>>     else if (action == Uninstall_action)
>>>       {
>>>         desired = packageversion ();
>>> +      pick (false);
>>> +      srcpick (false);
>>> +      if (!installed)
>>> +    action = NoChange_action;
>>
>> Hmm... why is adding this needed?
> 
> Otherwise a strange state change would occur at least in the GUI when an 
> install request is undone:
> 
> "Skip" == Ctrl+I ==> "3.2-1" == Ctrl+U ==> "Uninstall"
> 
> The new patch includes another addition which prevents this on installs 
> from local directory when the current default version is not yet 
> downloaded:
> 
> "Skip" == Ctrl+I ==> "" (empty)

I see.  But these work correctly when chosen via the action menu 
dropdown?  I forget how this all works, and there probably are separate 
paths which duplicate stuff, but this suggests to me that this is 
increasing that duplication, which isn't the desired direction of travel...

> BTW, I didn't understand this line:
> 
>    void
>    packagemeta::set_action (...)
>    {
>      ...
>      else if (action == Install_action)
>        {
>          desired = default_version;
>          if (desired)
>            {
>              if (desired != installed)
>                if (desired.accessible ())
>                  {
>                    ...
>                    pick (true);
>                    srcpick (false);
>                  }
>                else
>                  {
>                    pick (false);
>                    srcpick (true); <== why true? ==
>                  }
>                ...
> 

Yeah, I don't understand why that's there either.  It seems like it's 
going to give you the source package if you've asked for the package to 
be installed, but it's not available.

I think It's some ancient cruft which nobody would notice if we removed :)

  reply	other threads:[~2022-08-23 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-14 11:57 Christian Franke
2022-08-15 17:49 ` Jon Turney
2022-08-22 15:29   ` Christian Franke
2022-08-23 15:16     ` Jon Turney [this message]
2022-08-23 16:44       ` Christian Franke
2022-08-26 13:33         ` Jon Turney

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=cca37e6e-2db2-79eb-47d5-d094c586c2ed@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).