unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [sdl.web@gmail.com: Re: problem with transparent PNG image display]
Date: Wed, 01 Aug 2007 10:30:38 -0400	[thread overview]
Message-ID: <E1IGFDi-0005Ls-O9@fencepost.gnu.org> (raw)
In-Reply-To: <46A527C9.7040401@gnu.org> (message from Jason Rumney on Mon, 23 Jul 2007 23:12:25 +0100)

[I sent this message a week ago but did not get a response.
Could we get the discussion moving again?]

    When no background color is saved in the image, we render using the
    background color of the face the image is first drawn with, so the
    problem is not immediately apparent with those images, but if you draw
    the same image object onto a different colored background, you will see
    the same problem occur.

The cache could record what background color was used for rendering.
Then, on displaying the image again, if the desired background is
different, that could cause a cache-mismatch, which would cause
re-rendering.

For efficiency, we should do that only for formats that allow
transparency.

Is it possible to tell easily whether a png image has any
transparency?  Then we could optimize the images that don't
have any transparency by not recording a background for it.

    I don't know which platforms will let us cache image objects with
    transparency, but the solution would be to do that, and draw the
    background separately each time the image is drawn.

There must be something I don't get.  What would stop us from caching
the actual image data, transparent or not?

Is the idea that we want to save the time to re-render the image?

  parent reply	other threads:[~2007-08-01 14:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 18:07 [sdl.web@gmail.com: Re: problem with transparent PNG image display] Richard Stallman
2007-07-23 22:12 ` Jason Rumney
2007-07-24 16:45   ` Richard Stallman
2007-07-31 20:22   ` Richard Stallman
2007-07-31 21:30     ` Jason Rumney
2007-08-01 14:30       ` Richard Stallman
2007-08-01 14:30   ` Richard Stallman [this message]
2007-08-01 14:43     ` Miles Bader
2007-08-01 15:55       ` Jason Rumney
2007-08-02  0:36         ` YAMAMOTO Mitsuharu
2007-08-06 16:05     ` Chong Yidong
2007-08-06 16:41       ` Jason Rumney
2007-08-06 17:29         ` Chong Yidong
2007-08-06 20:14           ` Jason Rumney
2007-08-07 15:56             ` Chong Yidong
2007-08-07  1:21       ` Richard Stallman
2007-08-07 16:51         ` Chong Yidong
2007-08-26  0:50 ` Leo
  -- strict thread matches above, loose matches on Subject: below --
2007-06-24 23:47 Richard Stallman

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=E1IGFDi-0005Ls-O9@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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 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).