Andre Poenitz wrote: > On Fri, Mar 21, 2003 at 05:08:52PM +0100, Alfredo Braunstein wrote: >> If not, I have the feeling that a better solution can exist, like O(1) >> keeping only the y coordinate of one row. > > The row should cache its size, at it should be re-computed in the > metrics() phase...
The row does caches its size right now (and it's recomputed on rebreaking (=metrics if I understand correctly), we were talking about the y position. We need this y position cheaply for several things, including mapping between screen coordinates and real text. We were discussing the posibility of letting the row cache its y position as well. What do you think about that? Regards, Alfredo
