Abdelrazak Younes wrote: > Alfredo Braunstein wrote: >> Abdelrazak Younes wrote: >> >>> NoUpdate and SingleParUpdate are about _text_ _metrics_ updating, its a >>> Cursor thing. ScreenUpdateStrategy should be only about screen updating, >>> so it's a frontend thing and BufferView make the link between the two. I >>> introduced ScreenUpdateStrategy in order to cope with the decoration >>> update case. I agree there's some confusion there though; we can >>> revisite that field in 1.6 when we cleanup the "rowpainter". >> >> I think that the question is rather: "Why are we using NoScreenUpdate for >> painting stuff?" ;-) > > Hum... actually we don't ;-) > > NoScreenUpdate is just a way to reset the ScreenUpdateStrategy.
If we really aren't, then the patch from Stefan (at the top of this thread) shouldn't make any difference. But it does. A/
