This bug has been around for a long time. Basically there is some interaction that is causing the toolbar to get a continuous stream of paint events, or something like that, and that is what is consuming the CPU. To work around it you can just set the other direct children of the frame to be double buffered, but not the toolbar nor the frame itself.
IIRC, this has been fixed for 2.9.1.
···
On 6/9/10 1:03 PM, fabio67 wrote:
wxPython 2.8.11.0 unicode wxMSW Python 2.6.4
calling toolbar.SetDoubleBuffered(True) produces some kind of idle
loop and the CPU goes to 50% on a dual core system
easy to reproduce: add the following line in the toolbar demo code at
line 84
tb.SetDoubleBuffered(True)
then run the demo and measure the CPU load of pythonw.exe