Is fvwm double buffered or not?

[noguardkenny]

No matter how rarely I update text through fvwmscript I end up seeing some flickering from time to time when it updates. It reminds me of when I tried to make a rendering engine without double buffering.
So my question is: Is fvwm or more specifically fvwmscript updates double buffered?

[ftonneau]

There was some discussion of this issue here:

eliminating flicker in FvwnButtons and icons

I was curious if there is a way to eliminate flicker in various places in Fvwm, specifically FvwmButtons and icons. Flicker occurs in a few places, for instance: My clock is powered by a FvwmScript that is updated every minute, that is swallowed inside a FvwmButton. Everytime it updates you can see a very quick flicker. I have an image that sits inside a FvwmButton. I have it set so if I click on an area on my desktop this image will slide into view. The image slides in very clean, but…

So no, no double buffering AFAIK.

[ftonneau]

A follow-up comment:

In my own setup, I have two separate bars:

1. A tint2 bar for icon/message updates (e.g., RAM, battery, and date/time) that are clock-based.

2. A FVWM bar for icon/message updates (e.g., volume, luminosity, etc.) that depend on key presses (e.g. volume up/down, luminosity up/down) or window input.

Thus, I combine the best of both worlds :-). The tint2 bar is clock-based and does not flicker because tint2 is double-buffered. The FVWM bar is not double-buffered but does not flicker, because its content is updated only in response to keyboard or window events.