On Wed, Feb 4, 2009 at 8:18 AM, Edward K. Ream <[email protected]> wrote:
> > > I'll attempt, one more time, to do reduce scrolling. Yesterday's > "conclusions" mean nothing now... Rev 1516 contains a counter-intuitive change: it scrolls the present item in setItemForCurrentPosition even if the item is already the current position. The effect of this "extra" scrolling is to *reduce* jump. I think the present code is quite good. Imo, to better, we shall likely have to manage the scroll region by hand. Not fun, but doable, but not today. I've been shooting from the hip with these changes: I really do want to do isearch now. Feel free to experiment as you like... Edward P.S. I suspect, but don't know for sure, that some of the jump is due to QTreeWidget "optimizing" the amount of the tree is visible. For example, if a contract results in unused space at the bottom of the tree, QTreeWidget will scroll the present item even if no explicit scroll is requested. So managing the scroll region by hand may be the only way to reduce all jumps on contracts. I could be dead wrong though: I've changed the code too much recently to say anything for certain :-) That's all, **I hope**, for now... EKR --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
