unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>,
	emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: [PATCH] Delayed loading of image libraries
Date: 02 Jul 2004 09:10:55 +0200	[thread overview]
Message-ID: <x5oemyubnk.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20040702085419.CF31.JMBARRANQUERO@wke.es>

Juanma Barranquero <jmbarranquero@wke.es> writes:

> On Fri, 02 Jul 2004 10:16:03 +0900
> Miles Bader <miles@lsi.nec.co.jp> wrote:
> 
> > Previously, the value returned by `create-image' was a valid
> > image, which could be displayed, even if saved to a file and read
> > back in a new emacs session.  After your change for windows, this
> > was not true any longer.
> 
> Why?  In which way would it be different from the previous
> situation, where you could make a PNG image, say, save it, and load
> it on an Emacs *not* supporting PNG?

In that we are not talking about an Emacs not supporting PNG.  It is
fine if an Emacs not supporting PNG does not display a PNG.  It is
not fine if an Emacs supporting PNG does not display a PNG.

> After loading, Emacs *must* ask at a moment or other whether the
> image type is available, mustn't it?

How about when displaying it?

> So, at what moment is the loaded image used, and why
> `image-type-available-p' has not been called at that point?

Why should image-type-available-p have been called?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2004-07-02  7:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10 12:38 [PATCH] Delayed loading of image libraries Juanma Barranquero
2004-06-30 10:15 ` Andreas Schwab
2004-06-30 11:13   ` Juanma Barranquero
2004-06-30 11:24     ` Andreas Schwab
2004-06-30 11:34       ` Juanma Barranquero
2004-06-30 11:41         ` Andreas Schwab
2004-06-30 13:00           ` Juanma Barranquero
2004-06-30 15:42         ` Miles Bader
2004-07-01  9:30           ` Juanma Barranquero
2004-07-01  9:48             ` Miles Bader
2004-07-01 10:13               ` Juanma Barranquero
2004-07-02  1:16                 ` Miles Bader
2004-07-02  7:02                   ` Juanma Barranquero
2004-07-02  7:10                     ` David Kastrup [this message]
2004-07-02  7:41                       ` Juanma Barranquero
2004-07-02  7:56                         ` Miles Bader
2004-07-02  8:10                           ` Juanma Barranquero
2004-07-02  8:20                             ` Miles Bader
2004-07-02  8:45                               ` Juanma Barranquero
2004-07-02  8:59                                 ` Miles Bader
2004-07-02  9:02                                   ` Miles Bader
2004-07-02  8:11                         ` David Kastrup
2004-07-02  8:34                           ` Juanma Barranquero
2004-07-03 18:21                     ` Richard Stallman
2004-06-30 14:19       ` Stefan

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=x5oemyubnk.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=schwab@suse.de \
    /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).