public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: X/Cygwin icon proposal
Date: Sat, 20 Mar 2004 00:12:00 -0000	[thread overview]
Message-ID: <405B4523.8030903@msu.edu> (raw)
In-Reply-To: <B74CF8E243E50A43B2562370EBD9DBEC15A4C3@heis-2000server.heis.co.uk>

Phil Betts wrote:

> Hi Harold,
> 
> First off, as this is my first submission to the list, I'd like to
> extend my thanks
> to you and all of the other contributors to Cygwin/X.

Glad you like it.

>>Harold L Hunt II wrote:
>>1) A Japanese user has reported that the new icon was garbled on his 
>>Windows NT (I believe) system.  This is an isolated case so far and I 
>>think it is due to something with that particular system and is not 
>>something that we should worry about unless it starts getting reported
> 
> more.
> 
> This is a pretty mature list, followed by the sort of people who can
> resist the
> urge to send in "me too" messages.  I suspect that there are others like
> me who
> saw the original fault report and thought "OK, it's been logged already,
> I'll await
> the results".  Therefore, please don't discount solitary fault reports.

I have to discount them... I can't think of everything that gets 
reported once as a bonifed problem.  You are right, the list is mature, 
but people should know that *at least one other person* should speak up 
to verify that they also have the same problem as another is reporting. 
  This is essential and I am pretty amazed that no one did speak up in 
this case, until now.

  > FWIW, here are my observations on the discussion so far:
> 
> a) It makes no sense to inflict a random splodge on users of older OSes,
> just
> because a newer OS is able to display a prettier version of the current
> icon.

As I have said before, this is a technical question getting lots of 
personal and emotional answers.  Let me make this perfectly clear for 
everyone that is getting tied up on this issue:

1) Possible to have alpha icon that doesn't mess with older versions of 
Windows --> Our default icon will have alpha versions.

2) Alpha icons always mess with older versions of windows --> Our 
default icon will *not* have alpha versions.

There is no room for discussion on this, it is a simple technical 
question of "is this possible or not".

Please, refrain from discussing personal opinions, speculation about 
what version of Windows people are using, etc.  I have always aimed to 
support the minimum subset of features available on all versions of 
Windows since 95 and I am not going to deviate from that on the icon issue.

> b) As a user of an older OS, I would gladly live with an amorphous
> blotch if you
> could get the clipboard to work with emacs!

Umm... the clipboard should work with emacs... if it does not, then that 
is a problem.  You are using the -clipboard parameter from a recent 
version (xserv-4.3.0-59) and *not* using xwinclip, right?  This was 
fixed ages ago if you are referring to the selection highlight disappearing.

Harold


       reply	other threads:[~2004-03-19 19:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B74CF8E243E50A43B2562370EBD9DBEC15A4C3@heis-2000server.heis.co.uk>
2004-03-20  0:12 ` Harold L Hunt II [this message]
2004-03-19 16:10 Orrigo, Giampaolo .
  -- strict thread matches above, loose matches on Subject: below --
2004-03-19  5:45 Michael Bax
2004-03-19  5:49 ` Harold L Hunt II
2004-03-19 14:53   ` Igor Pechtchanski
2004-03-19 17:59 ` Jehan Bing
2004-03-18 23:39 Earle F. Philhower, III
2004-03-18 23:51 ` Harold L Hunt II
2004-03-19  2:48 ` Nahor
2004-03-18 23:14 Earle F. Philhower, III
2004-03-18 23:22 ` Harold L Hunt II
2004-03-18 20:43 Earle F. Philhower, III
2004-03-18 22:26 ` Nahor
     [not found] <IMEDKPLHDOLIKADDEMBGKEGBCEAA.bax3.NO@SPAM.bigfoot.com>
     [not found] ` <c3cl67$i8g$1@sea.gmane.org>
2004-03-18 17:43   ` Alexander Gottwald
2004-03-18 18:15     ` Nahor
2004-03-18 19:12       ` Alexander Gottwald
2004-03-18 19:30         ` Harold L Hunt II
2004-03-18 18:46   ` Benjamin Riefenstahl
     [not found] <IMEDKPLHDOLIKADDEMBGCEDBCEAA.bax3.NO@SPAM.bigfoot.com>
     [not found] ` <c2l08r$s95$1@sea.gmane.org>
2004-03-10  2:44   ` Harold L Hunt II
2004-03-10  3:02     ` Nahor
2004-03-10  3:18       ` Harold L Hunt II
     [not found]         ` <c2nko7$uba$1@sea.gmane.org>
2004-03-10 18:00           ` Harold L Hunt II
     [not found]             ` <c2nm3d$2kg$1@sea.gmane.org>
2004-03-11 13:20               ` Benjamin Riefenstahl
     [not found]                 ` <c2qaku$c5c$1@sea.gmane.org>
2004-03-11 19:33                   ` Benjamin Riefenstahl
2004-03-11 20:07                     ` Alexander Gottwald
2004-03-11 21:24                       ` Nahor
2004-03-11 21:34                         ` Harold L Hunt II
2004-03-12  6:09                           ` Earle F. Philhower III
2004-03-12  6:14                             ` Harold L Hunt II
2004-03-12  6:48                               ` Earle F. Philhower III
2004-03-13  8:30                                 ` Earle F. Philhower III
2004-03-13  9:50                                   ` Harold L Hunt II
2004-03-12 12:59                         ` Benjamin Riefenstahl
2004-03-12 16:51                           ` Nahor
2004-03-12 17:42                             ` Benjamin Riefenstahl
2004-03-12 17:49                       ` Benjamin Riefenstahl
2004-03-09  1:34 David Arnstein
2004-03-09  4:39 ` Igor Pechtchanski

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=405B4523.8030903@msu.edu \
    --to=huntharo@msu.edu \
    --cc=cygwin-xfree@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).