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?" ;-) A/
