From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Status of MAC/W32/X consolidation -- first major patch committed.
Date: 17 Mar 2003 00:59:24 +0100 [thread overview]
Message-ID: <5x3clmrhgj.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <m21y17x7yp.fsf@nyaumo.jasonr.f2s.com>
Jason Rumney <jasonr@gnu.org> writes:
> As part of your changes, you introduced the following function:
>
> static void
> w32_get_glyph_overhangs (glyph, f, left, right)
> struct glyph *glyph;
> struct frame *f;
> int *left, *right;
> {
> HDC hdc = get_frame_dc (f);
> /* Convert to unicode! */
> x_get_glyph_overhangs (glyph, f, left, right);
> release_frame_dc (f, hdc);
> }
>
> What does the comment "Convert to unicode!" mean? Is there work
> required to properly convert this to Windows? If that is the case, I
> don't know when I would get time to look at it, and it will probably
> get forgotten. It would be better to revert that part of the change.
I didn't "invent" that comment... it was there already.
The above function used to be named "x_get_glyph_overhangs" calling
what used to be named "w32_get_glyph_overhangs".
I swapped the names of "w32_get_glyph_overhangs" and
"x_get_glyph_overhangs" to make the X and W32 code less different...
>
> As it is, the function is not needed. Since hdc is never used, there
> is no point retrieving and releasing it. So we might as well use
> x_get_glyph_overhangs directly.
>
I thought so myself, but it could seem like get_frame_dc had some
side-effects, so I didn't want to break anything. If you think it is
safe to discard w32_get_glyph_overhangs, just do it!
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2003-03-16 23:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 12:13 Status of MAC/W32/X consolidation and some questions Kim F. Storm
2003-03-10 17:00 ` Andrew Choi
2003-03-11 1:06 ` Kim F. Storm
2003-03-11 15:31 ` Andrew Choi
2003-03-10 17:09 ` Andrew Choi
2003-03-11 1:04 ` Kim F. Storm
2003-03-11 15:40 ` Andrew Choi
2003-03-10 17:23 ` Benjamin Riefenstahl
2003-03-11 1:01 ` Kim F. Storm
2003-03-11 0:19 ` Juanma Barranquero
2003-03-11 10:35 ` Kim F. Storm
2003-03-11 10:07 ` Jason Rumney
2003-03-11 11:09 ` Kim F. Storm
2003-03-12 4:47 ` Miles Bader
2003-03-11 0:03 ` Jason Rumney
2003-03-11 1:47 ` Miles Bader
2003-03-11 19:03 ` Stefan Monnier
2003-03-12 4:44 ` Miles Bader
2004-07-22 15:11 ` Kim F. Storm
2004-07-22 21:40 ` Miles Bader
2003-03-11 14:19 ` Kim F. Storm
2003-03-12 19:27 ` Eli Zaretskii
2003-03-12 23:01 ` Kim F. Storm
2003-03-16 22:00 ` Status of MAC/W32/X consolidation -- first major patch committed Kim F. Storm
2003-03-16 22:27 ` Jason Rumney
2003-03-16 23:59 ` Kim F. Storm [this message]
2003-03-17 8:56 ` Jason Rumney
2003-03-17 11:40 ` Kim F. Storm
2003-03-17 14:56 ` Benjamin Riefenstahl
[not found] ` <1047913554.3e75e4529bc88@webmail.freedom2surf.net>
2003-03-17 16:43 ` Benjamin Riefenstahl
2003-03-17 19:01 ` Juanma Barranquero
2003-03-21 15:10 ` Status of MAC/W32/X consolidation -- second " Kim F. Storm
2003-03-21 16:46 ` Juanma Barranquero
2003-03-21 22:48 ` Kim F. Storm
2003-03-24 20:07 ` Andrew Choi
2003-03-31 22:16 ` Status of MAC/W32/X consolidation -- third " Kim F. Storm
2003-04-01 1:13 ` Andrew Choi
2003-04-01 9:27 ` Kim F. Storm
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=5x3clmrhgj.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--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.