From: Alan Third <alan@idiocy.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Native image rotation
Date: Mon, 20 May 2019 19:18:48 +0100 [thread overview]
Message-ID: <20190520181848.GA18876@breton.holly.idiocy.org> (raw)
In-Reply-To: <87mujikx2p.fsf@tcd.ie>
On Sun, May 19, 2019 at 09:29:02PM +0100, Basil L. Contovounesios wrote:
> Alan Third <alan@idiocy.org> writes:
>
> > On Mon, Feb 25, 2019 at 07:21:02PM +0000, Alan Third wrote:
> >> On Mon, Feb 25, 2019 at 05:36:46AM +0200, Eli Zaretskii wrote:
> >> >
> >> > It's indeed the clearing that bothered me,
> >>
> >> Would it be better if it was done by another XRender composite rather
> >> than x_clear_area?
> >
> > I tried to replace this with XRenderFillRectangle, but realised I need
> > to construct an XRenderColor struct, and I’ve no idea how to get the
> > colour data held in img->background.
> >
> > I’ve attached a patch containing the original two, and the ability to
> > crop.
>
> Thanks for working on this; I'm curious to know its status.
I’ve sort of put Emacs development on a back burner for the moment.
I’m planning on returning to this at some point, though.
> BTW, I think native image rotation should support arbitrary angles (if
> possible), if for no other reason than ImageMagick also supporting them.
I do think there is an issue with masks and cursors that maybe
wouldn’t be straight forward. I’m still somewhat unclear on how
images, cursors and masks interact. If someone has a good solution I’d
be happy to hear it, but of course it has to be passed by Eli too and
I don’t know if his objections are the same as what I’m thinking of.
I plan to go back and rewrite it to only handle 90 degree increments
and submit that, at least for now.
--
Alan Third
next prev parent reply other threads:[~2019-05-20 18:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 11:30 Native image rotation Alan Third
2019-02-24 16:14 ` Eli Zaretskii
2019-02-24 17:34 ` Clément Pit-Claudel
2019-02-24 17:49 ` Eli Zaretskii
2019-02-24 18:06 ` Clément Pit-Claudel
2019-02-24 18:28 ` Eli Zaretskii
2019-02-24 18:51 ` Stefan Monnier
2019-02-24 19:13 ` Eli Zaretskii
2019-02-24 19:23 ` Eli Zaretskii
2019-02-24 20:08 ` Stefan Monnier
2019-02-24 23:00 ` Alan Third
2019-02-25 3:32 ` Eli Zaretskii
2019-02-24 23:22 ` Alan Third
2019-02-25 3:36 ` Eli Zaretskii
2019-02-25 5:11 ` Van L
2019-02-25 13:47 ` Stefan Monnier
2019-02-25 19:21 ` Alan Third
2019-02-26 17:01 ` Daniel Pittman
2019-03-02 13:29 ` Alan Third
2019-05-19 20:29 ` Basil L. Contovounesios
2019-05-20 18:18 ` Alan Third [this message]
2019-05-21 20:11 ` Alan Third
2019-06-02 18:11 ` Alan Third
2019-06-02 18:24 ` Lars Ingebrigtsen
2019-06-05 21:39 ` Alan Third
2019-06-06 9:03 ` Andy Moreton
2019-06-06 12:57 ` Eli Zaretskii
2019-05-22 6:45 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-02-25 12:48 Evgeny Zajcev
2019-02-25 15:43 ` Clément Pit-Claudel
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=20190520181848.GA18876@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=contovob@tcd.ie \
--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).