From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH setup] Show a MessageBox warning if running on a deprecated Windows version
Date: Mon, 24 Jan 2022 19:57:13 +0000 [thread overview]
Message-ID: <1e5b78f8-e507-514e-d524-cc390818933a@dronecode.org.uk> (raw)
In-Reply-To: <1b6219e5-21ec-8b54-b34a-4b5978e6c864@dronecode.org.uk>
On 18/01/2022 16:15, Jon Turney wrote:
> On 14/01/2022 09:04, Corinna Vinschen wrote:
>> On Jan 13 15:13, Jon Turney wrote:
>>> Show a MessageBox warning if we are running on a Windows version which
>>> we have deprecated Cygwin support for:
>>>
[..]
>>
>> Question is, how often should setup show this message? Every time might
>> really be a bit annoying. Some kind of "I saw it, now leave me alone,
>> at least for a while" kind of function would be great.
>
> Yeah, unfortunately that turns this into more effort than I'm going to
> commit to this:
>
> Adding a "Don't show this again" checkbox means we can't use a
> MessageBox, so have design a dialog box for that purpose.
>
> Making that setting persistent means we have to wait until after the
> cygwin root directory is established so we know where to retrieve that
> persistent setting from.
It turns out SHMessageBoxCheck() exists, which avoids both these
problems, so I've reworked this change to use that.
prev parent reply other threads:[~2022-01-24 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 15:13 Jon Turney
2022-01-14 9:04 ` Corinna Vinschen
2022-01-14 10:54 ` Adam Dinwoodie
2022-01-14 11:45 ` Corinna Vinschen
2022-01-16 13:46 ` Adam Dinwoodie
2022-01-16 17:55 ` Hamish McIntyre-Bhatty
2022-01-17 10:03 ` Corinna Vinschen
2022-01-17 18:06 ` Brian Inglis
2022-01-18 16:15 ` Jon Turney
2022-01-24 19:57 ` Jon Turney [this message]
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=1e5b78f8-e507-514e-d524-cc390818933a@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).