[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Pixel-based display functions
From: |
Eli Zaretskii |
Subject: |
Re: Pixel-based display functions |
Date: |
Mon, 02 Feb 2015 17:58:28 +0200 |
> From: Lars Ingebrigtsen <address@hidden>
> Cc: Stefan Monnier <address@hidden>, address@hidden
> Date: Mon, 02 Feb 2015 20:46:51 +1100
>
> > I explicitly mentioned vertical-motion in one of my previous messages,
> > and explained there how to use it to find buffer position that
> > corresponds to a given pixel coordinate. Lars said it wasn't what he
> > needed, I don't know why.
>
> I think I asked whether it was another one of those functions that only
> report the position after redisplay has taken place, and if so, it's not
> usable for this use case.
>
> If it does report the position before redisplay has happened
It does.
In general, very few functions require an up-to-date display for doing
their job; those that do have that fact stated in their doc strings.
I hope you noticed my comments about the visual vs logical order:
vertical-motion is one of the functions that work in visual order.
- Re: Pixel-based display functions, Stefan Monnier, 2015/02/01
- Re: Pixel-based display functions, martin rudalics, 2015/02/01
- Re: Pixel-based display functions, Lars Ingebrigtsen, 2015/02/01
- Re: Pixel-based display functions, martin rudalics, 2015/02/01
- Re: Pixel-based display functions, Eli Zaretskii, 2015/02/01
- Re: Pixel-based display functions, martin rudalics, 2015/02/01
- Re: Pixel-based display functions, Eli Zaretskii, 2015/02/01
- Re: Pixel-based display functions, martin rudalics, 2015/02/01