unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Interest in nt_load_image?
Date: Tue, 31 Mar 2020 01:21:34 +0200	[thread overview]
Message-ID: <CAAeL0STfSuQxFGAGzS9w1ZJgk6ziXA61E-ze6Kk5zT0YFq4p8g@mail.gmail.com> (raw)
In-Reply-To: <86r1x9rf7w.fsf@csic.es>

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

On Mon, Mar 30, 2020 at 6:17 PM Juan José García-Ripoll <
juanjose.garciaripoll@gmail.com> wrote:

> if GDI+ support is dropped in
> the near future (which I doubt, given it is also supported by Direct2D),
it can
> be almost trivially replaced with Windows Image Component, which is the
more
> modern interface.

Is there any advantage in using Windows Imaging Component?

I mean, if as Eli suggests you're going to dynamically check for GDI+
support and revert back to the current API in Windows 9X, it is feasible to
check for Windows Imaging Component when Emacs runs on modern Windows and
use it if available? Does it offer any advantage?

Just curious.

[-- Attachment #2: Type: text/html, Size: 899 bytes --]

  parent reply	other threads:[~2020-03-30 23:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 19:33 Interest in nt_load_image? Juan José García-Ripoll
2020-03-29 21:55 ` Juan José García-Ripoll
2020-03-30  2:21 ` Eli Zaretskii
2020-03-30  7:54   ` Juan José García-Ripoll
2020-03-30 13:46     ` Eli Zaretskii
2020-03-30 14:36       ` Juan José García-Ripoll
2020-03-30 14:44         ` Juan José García-Ripoll
2020-03-30 15:50         ` Eli Zaretskii
2020-03-30 16:15           ` Juan José García-Ripoll
2020-03-30 16:37             ` Eli Zaretskii
2020-03-30 17:16               ` Stefan Monnier
2020-03-30 18:32                 ` Eli Zaretskii
2020-03-30 18:41                   ` Stefan Monnier
2020-03-30 18:57                     ` Eli Zaretskii
2020-03-30 19:39                       ` Stefan Monnier
2020-03-31 14:19                         ` Eli Zaretskii
2020-03-30 18:06               ` Juan José García-Ripoll
2020-03-30 18:47                 ` Eli Zaretskii
2020-03-30 18:53                   ` Eli Zaretskii
2020-03-30 23:21             ` Juanma Barranquero [this message]
2020-03-31  8:01               ` Juan José García-Ripoll
2020-03-31 13:14                 ` Juanma Barranquero
2020-03-31 14:50                   ` Stefan Monnier
2020-03-31 15:25                     ` Juanma Barranquero
2020-03-31 16:54                       ` Stefan Monnier
2020-03-31 15:13                   ` Juan José García-Ripoll
2020-03-31 15:28                     ` Juanma Barranquero
2020-03-31 13:31                 ` Eli Zaretskii
2020-03-30 15:14       ` Stefan Monnier
2020-03-30 15:57         ` Eli Zaretskii
2020-03-30 17:10           ` Stefan Monnier
2020-03-30 18:23             ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAeL0STfSuQxFGAGzS9w1ZJgk6ziXA61E-ze6Kk5zT0YFq4p8g@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juanjose.garciaripoll@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).