From: David Abrahams <dave@boost-consulting.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PING] ClearType Patch
Date: Wed, 08 Jun 2005 11:46:58 -0400 [thread overview]
Message-ID: <ur7fcetql.fsf@boost-consulting.com> (raw)
In-Reply-To: <ud5qwapgc.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 08 Jun 2005 17:33:07 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: David Abrahams <dave@boost-consulting.com>
>> Date: Wed, 08 Jun 2005 09:45:16 -0400
>>
>> Sorry to be a pest, but as easy as it was, solving this problem did
>> take significant effort on my part.
>
> Thank you for your work.
>
> However, with only a few days past, you could have waited a few more
> before deciding that your patches were ignored.
Sorry, but I have a lot on my plate, so once I start waiting a few
more days it's likely to drop off my radar screen.
>> So could someone please either render a judgement about how the patch
>> should be changed, or check it in as is, or give me CVS write
>> permission so I can do it myself?
>
> I'm bothered by the funky W32_* macros, so I'd like to hear from
> people who know more than myself about the intricacies of MSVC and
> MinGW whether there's no cleaner way to do this. Hard-coding macros
> from system headers (that's what those #define's are, right?)
Yep.
> in Emacs doesn't sound like a good idea to me.
Agreed, but I think the use of -D_WIN32_WINNT=0x0400 on the compiler
command-line may be similarly bad (and is the reason I transcribed
those constants).
> Also, according to what I see in the MinGW headers, I'm not sure I
> understand the problem. I see SPI_GETFONTSMOOTHING in winuser.h,
> whose definition is unaffected by the value of _WIN32_WINNT.
I'm compiling with msvc 7.1; I don't know what MinGW does.
> I don't
> see the other two constants in the MinGW headers. So please explain
> in more detail the problem that caused you to define your own macros:
> what macros you wanted to use,
SPI_GETFONTSMOOTHING
This one is in fact available for _WIN32_WINNT == 0x400; I should
have used it directly.
SPI_GETFONTSMOOTHINGTYPE
FE_FONTSMOOTHINGCLEARTYPE
These two are only enabled for _WIN32_WINNT >= 0x0501
> where they are defined,
WinUser.h, IIRC
> and why the value of _WIN32_WINNT prevents you from using them.
Because they are #ifdef'd out when _WIN32_WINNT takes certain values.
> Finally, MSDN seems to indicate that SPI_GETFONTSMOOTHINGTYPE is
> unsupported on Windows 9x, so it sounds like your code should be
> disabled for those versions of Windows.
Right, I should use an #ifdef _WIN32_WINNT >= 0x0501 ... except of
course that the build process subverts that by forcing _WIN32_WINNT to
0x400.
> A ChangeLog entry for the patches would also be nice, btw.
I will be happy to write one. I assume the format to follow is used
in the ChangeLog file at the top of emacs' CVS tree?
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next prev parent reply other threads:[~2005-06-08 15:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 12:38 Emacs defeats ClearType David Abrahams
2005-06-03 8:30 ` jasonr
2005-06-03 10:54 ` David Abrahams
2005-06-03 15:22 ` jasonr
2005-06-03 15:27 ` David Abrahams
2005-06-06 15:47 ` jasonr
2005-06-06 16:46 ` David Abrahams
2005-06-07 1:15 ` Miles Bader
2005-06-07 13:20 ` David Abrahams
2005-06-08 13:45 ` [PING] ClearType Patch David Abrahams
2005-06-08 14:33 ` Eli Zaretskii
2005-06-08 15:46 ` David Abrahams [this message]
2005-06-08 16:44 ` Stefan Monnier
2005-06-08 20:01 ` David Abrahams
2005-06-08 18:22 ` Eli Zaretskii
2005-06-08 19:57 ` David Abrahams
2005-06-08 21:29 ` jasonr
2005-06-08 21:23 ` jasonr
2005-06-08 22:17 ` David Abrahams
2005-06-09 8:10 ` jasonr
2005-06-11 13:12 ` Eli Zaretskii
2005-06-11 16:50 ` David Abrahams
2005-06-15 7:15 ` David Abrahams
2005-06-15 9:19 ` David Abrahams
2005-06-18 23:02 ` How is highlighting done in show-paren-mode? David Abrahams
2005-07-14 18:55 ` Who can explain the display architecture? David Abrahams
2005-07-15 9:41 ` Kim F. Storm
2005-06-08 23:34 ` [PING] ClearType Patch Stefan Monnier
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=ur7fcetql.fsf@boost-consulting.com \
--to=dave@boost-consulting.com \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.