GTK has double buffering already. (if you do not turn it of every GTK widget)
BUT only the visible area is buffered, as I found out, if you scroll a new area gets visible, then it has to be painted. Because of this I render the whole page first to an Image. Evince also do this... Double buffering is useful if you e.g. move a window over your window, then the window has to be repaint. On windows you often can see strange things, even on windows 7 its nod double buffered, if you have a slow PC or so you can see it has to repaint the application after you moved a window over another window. If you use windows you for sure saw this;-) This will GTK do automatically with double buffering. Andreas Am 17.01.2011 20:09, schrieb Aniello Del Sorbo: > I haven't yet look at why, but my port to Maemo (they use GTK+ > natively with their Hildon UI) has a pretty slow refresh when > scrolling the canvas. > Someone from Nokia suggested me to use double buffering, but I thought > libgnomecanvas would take care of that already. > ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Xournal-devel mailing list Xournal-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xournal-devel
