John Levon wrote: > On Fri, Dec 03, 2004 at 10:38:12PM +0100, Alfredo Braunstein wrote: > >> Humm... right this is fault of the new coord scheme: now we don't know >> the full doc height so we cannot accurately compute the scrollbar height. >> I > > BTW, why did you decide to go this route, when other word processors can > keep accurate scrollbars? I'm sure there's a good reason, I'd just like > to hear it
1) I actually didn't decide. 2) How do you know that other word processors keep an accurate scrollbar, or in which sense you intend by accurate. It would probably suffice something reasonable/useable, nobody is counting pixels of offscreen text. 3) The reason is to avoid keeping updated y positions of every piece of the document -- meaning calling redoParagraph/fullRebreak in strategic places followed by updateParPositions, trying to avoid putting the latter in some inner loop. Aditionally it avoids completely the initial rebreak, improving loading times enormously. Now the scheme is much simpler: you never call these, all is taken care in update(). 4) Your timing is admirable Alfredo
