On Tue, Jan 14, 2003 at 05:33:26PM +0100, RvB wrote:
> On Tue, Jan 14, 2003 at 08:15:17AM +0100, Dominik Vogt wrote:
>
> hi :)
>
> > I guess you have to ask the Eterm developers about this.
>
> i think it is not actually an eterm problem, it also happens with rxvt
> and many similar programmes. it also happens to transparent window
> titlebars of fvwm. they are refreshed the whole time while moving, which
> takes a lot of cpu time. it would be a lot better if there was an option
> for the window to be refreshed after the move or resize is actually finished.
> :)
Really, fvwm is just honouring standards. Any decent
implementation of transparency (in an application) suppresses most
of these redraws.
> in other windowmanagers, (enlightenment, afterstep, wmaker, ...)
> "transparency" acts like this, and it is a lot resource-friendlier ...
> and as i said it is not an Eterm-specific problem :)
Right, then it's a problem in E, afterstep, wmaker, ... too. The
standard (ICCCM2) is very clear about the right behaviour. If
other WMs are ignoring this standard, it's their problem, not
fvwm's.
But to be honest I suspect that you are running very old versions
of Eterm, rxvt and said window managers. As far as I know, the
latest versions of the terminal programs have already been fixed.
Bye
Dominik ^_^ ^_^
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Jan 15 2003 - 01:07:54 GMT