Issue 81370

Summary: remove special lazy-paint
Product: Writer Reporter: max.odendahl
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: Armin.Le.Grand, issues, Mathias_Bauer, orw
Version: 680   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description max.odendahl 2007-09-07 15:47:58 UTC
As discussed with AW and mba, we should remove the special lazy-paint. This is
obsolete due to preRendering of new DrawingLayer
Comment 1 max.odendahl 2007-09-07 15:48:41 UTC
Change target to 2.4
Comment 2 andreas.martens 2007-11-19 13:12:31 UTC
Set Target to OOo3.0
Comment 3 andreas.martens 2008-04-28 12:53:27 UTC
Set target OOo3.x
Comment 4 max.odendahl 2009-03-30 10:55:16 UTC
mod->od: maybe this is one for you as well while doing the drawing stuff
refactoring? Should simplify code even more
Comment 5 Oliver-Rainer Wittmann 2009-03-30 13:14:31 UTC
May be ;-)
What is meant by "special lazy paint"? The creation and usage of a virtual
output, when the repaint area is small enough?
Comment 6 max.odendahl 2009-03-30 13:43:44 UTC
actually, I don't know, I just remember that writer is doing something specific
which is obsolete now with the new drawinglayer. As this description fits your
wiki page, I though I mention this issue :-)

But I guess mba/aw have more knowledge in this
Comment 7 Armin Le Grand 2009-03-30 14:03:00 UTC
AW: I do not know what is meant by 'special lazy-paint', but all cases where SW
is using an own VDev to buffer to avoid flickering can be (and should be)
removed. HTH!
Comment 8 Oliver-Rainer Wittmann 2009-04-03 14:22:14 UTC
This refactoring is nothing for my current planned refactoring of the Writer's
usage of the Drawing layer, but I volunteer to take over this issue.
Comment 9 Marcus 2017-05-20 11:15:19 UTC
Reset assigne to the default "".