From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: Cygwin Terminal icon broken on case-sensitive systems
Date: Sat, 31 Dec 2011 10:15:00 -0000 [thread overview]
Message-ID: <CAHWeT-ZqG-jd3i76z4MrFd7S-XD56VhKMPyYMPQnjv02_qaw8Q@mail.gmail.com> (raw)
In-Reply-To: <CAHWeT-ZX6sL1LMJsHQu1L7azLhwH1wwHMTLKpVCiQFNZBuAX4g@mail.gmail.com>
On 24 November 2011 16:10, Andy Koppe wrote:
> On 24 November 2011 15:42, Andy Koppe wrote:
>> I'm afraid there's a problem with the new "Cygwin Terminal" icon
>> (which I'm sorry not to have spotted when reviewing the change).
>>
>> Setup.exe creates the mintty shortcuts with '-i /Cygwin-Terminal.ico',
>> yet the icon file it creates is called 'cygwin-terminal.ico', i.e. all
>> lowercase. This means that users of systems with case sensitivity
>> enabled just get to see a dialog box saying "/usr/bin/mintty: could
>> not load icon from '/Cygwin-Terminal.ico'".
>
> Actually, I take it all back. I'd confused myself by still having a
> 'cygwin-terminal.ico' lying around from earlier experiments. Setup.exe
> does create it with the correct name.
>
>> Apparently at least two users have fallen foul of this already:
>>
>> http://georgik.sinusgear.com/2011/11/23/mintty-resizable-terminal-for-windows/
>
> Still leaves the question what's going on there.
I think I found what triggered this: with a non-default dpi setting,
for some reason the ExtractIconEx function used to load the icon
doesn't return a small version of the icon along with the normal one.
I (somewhat accidentally) fixed this in 1.0.3 by no longer insisting
on a small icon being returned, as it's optional when creating a
window class anyway.
Andy
prev parent reply other threads:[~2011-12-31 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 15:47 Andy Koppe
2011-11-24 16:10 ` Corinna Vinschen
2011-11-24 16:11 ` Andy Koppe
2011-12-31 10:15 ` Andy Koppe [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=CAHWeT-ZqG-jd3i76z4MrFd7S-XD56VhKMPyYMPQnjv02_qaw8Q@mail.gmail.com \
--to=andy.koppe@gmail.com \
--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).