I run Win7 64. When I run wz4 with Desktop composition on I have occasionally flickering menus. Any way to make an option to enable/disable double buffering? Or maybe some other way to fix this problem?

Here is what ryg wrote about it:
The Werkkzeug4 GUI (unlike Werkkzeug3) uses plain Windows GDI calls which draw directly to the screen without any double buffering (at least if Desktop Compositing, i.e. Aero, is off). When animated, Ops will continuously redraw (in case their caching state etc. changes). So, short version: this is expected and not properly fixable without using either double buffering (which forces GDI to use software rendering and is much slower overall) or very detailed dirty region tracking (which is a pain in the ass).

I found in the altona framework a simple option that disable the Vista/Win7 Desktop Window Manager. It stops the flickering on my config with win7 and good news it provide an interesting fps gain. I need to test on xp to see if this not provide any problem or if I need to test the system before set this option.

however on windows 8 the problem can't be fixed by this way.

see microsoft doc :

As of Windows 8, the information in this section is no longer valid. DWM (Desktop Window Manager) can no longer be programmatically disabled,

http://msdn.microsoft.com/en-us/library ... 85%29.aspx

In fact, in window 7 the problem is easily solved by setting Disable Desktop Composition to "On" in wz4 shortcut preferencies. When running wz4 it disables desktop composition for the whole windows theme. The problem is how to make wz work preperly with Disable Desktop Composition set to Off (i.e. the generic win7 display mode - desktop comp is on). Considering win8 doesn't allow us to disable Desktop Window Manager programmaticlly, and looking into the future, this problem should be addressed in some way...

yes i'm agree, but in wait of a better solution, this simple flag will do the trick.

OK. Let there be the flag for now. Thanks.

finally not a good idea to set this flag, because it desactivate the destop windows manager during all wz session.

OK. Hopefully some day this problem will be solved. Anyway, thanks for the effort.