From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Third <alan@idiocy.org>, emacs-devel@gnu.org
Subject: Re: Testing native image scaling
Date: Wed, 27 Mar 2019 11:35:26 +0900 [thread overview]
Message-ID: <wl5zs5avtd.wl-mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <834la3b9hd.fsf@gnu.org>
On Mon, 21 Jan 2019 01:05:18 +0900,
Eli Zaretskii wrote:
>
> > Date: Sat, 19 Jan 2019 21:45:43 +0000
> > From: Alan Third <alan@idiocy.org>
> > Cc: emacs-devel@gnu.org
> >
> > On Sat, Jan 19, 2019 at 11:31:34AM +0200, Eli Zaretskii wrote:
> > > Alan, could you please tell how you tested native image scaling with
> > > the XRENDER extension, and perhaps show some Lisp or existing commands
> > > you used for that? E.g., did the features in thumbs.el work for you
> > > in a build without Imagemagick?
> >
> > I just used a fairly simple series of commands like this:
> >
> > (setq i (create-image "~/image.png" nil nil :scale 0.5))
> > (insert-image i)
> > (setq ii (create-image "~/image.png" nil nil :scale 0.5))
> > (insert "\n")
> > (insert-image ii)
>
> Thanks, this was very helpful. (Actually, just create-image with one
> argument is enough: after inserting it, '+' or '-' on the image will
> interactively resize it.)
I think we should test sliced images as well.
(insert-sliced-image (create-image "splash.png" nil nil :scale 0.5) nil nil 3 5)
Actually, I suspect this does not work on W32 because the comparison
with the original image size is made for s->slice.width (or height)
rather than s->img->width (or height) as I just did for cairo code.
Could you check it on W32?
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2019-03-27 2:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 9:31 Testing native image scaling Eli Zaretskii
2019-01-19 21:45 ` Alan Third
2019-01-20 16:05 ` Eli Zaretskii
2019-01-20 19:26 ` Alan Third
2019-01-20 19:41 ` Eli Zaretskii
2019-01-20 20:19 ` Alan Third
2019-03-27 2:35 ` YAMAMOTO Mitsuharu [this message]
2019-03-27 17:09 ` Eli Zaretskii
2019-03-27 18:35 ` Andy Moreton
2019-03-27 18:42 ` Eli Zaretskii
2019-03-27 19:06 ` Andy Moreton
2019-03-27 19:34 ` Andy Moreton
2019-03-28 2:26 ` YAMAMOTO Mitsuharu
2019-03-28 16:02 ` Eli Zaretskii
2019-03-28 18:06 ` Andy Moreton
2019-03-28 18:19 ` Eli Zaretskii
2019-03-28 19:29 ` Andy Moreton
2019-03-28 20:09 ` 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=wl5zs5avtd.wl-mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=alan@idiocy.org \
--cc=eliz@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).