Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Abdelrazak Younes wrote:
| > | > Lars Gullik Bjønnes wrote:
| > | | >> Then we should have two differnt methods one that call update
| > and one
| > | >> that call repaint.
| > | >>
| > | >> On scroll-down we should not allow combining paint events.
| > | > The weird thing is that on Windows the all screen repaint are
| > | > acknowledged and done in sequence.
| > | >
| > | >> Perhaps a genereal rule is: if the whole workarea is to be painted,
| > | >> use repaint, if not, use update. That should be possible to put into
| > | >> sourcecode.
| > | > Maybe... Let me think a bit about that. I could make a special case
| > | > in "WorkArea::redraw()".
| > | | Now, I thought about it I think our use of update is correct. The
| > | problem you're facing is probably related to the fact that I called
| > | "viewport->update()" instead of "update()". I have added commented out
| > | the code in the former patch if it turns out that I am wrong so that
| > | you can try it.
| > | | This patch goes in now as it is obviously correct.
| > but it did not fix the problem.
|
| By the way, does someone else see this this problem?
I see it on FC5 both x86_64 and i386.
And the conditional repaint did not work, but I am not sure that it
triggers at all... testing...
--
Lgb
