As said, hardly any speed improvement noticed. Regards, Darius
On Feb 8, 2012, at 10:42 AM, Felipe Monteiro de Carvalho wrote: > On Wed, Feb 8, 2012 at 10:37 AM, Graeme Geldenhuys > <[email protected]> wrote: >> You didn't touch on my other point. Is double buffering enabled by >> default for all painting routines in the LCL? Or must the end-user / >> developers specifically enable it somewhere? > > He is using TImage, which is not built for fast changing graphics, it > is built for displaying a static image or images which change > sometimes only, so he is already using the wrong architecture. > > But the answer would be: depends. There is a DoubleBuffer property > which affects only Windows. I think that all other widgetsets always > do Double-buffering without an option to disable it. But TImage > probably already defines DoubleBuffer. His flickering could be due to > partial updates or background erasing. But summing up, his problem is > using the wrong component for the job, not the DoubleBuffer propery. > > -- > Felipe Monteiro de Carvalho > > -- > _______________________________________________ > Lazarus mailing list > [email protected] > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
