Re: FVWM: Everything stops when moving around windows

From: Dominik Vogt <fvwm_at_fvwm.org>
Date: Mon, 2 Dec 2002 17:58:26 +0100

On Mon, Dec 02, 2002 at 08:39:57AM -0800, Erik Steffl wrote:
> Dominik Vogt wrote:
> > On Sun, Dec 01, 2002 at 11:01:57PM -0800, Erik Steffl wrote:
> > > Mikhael Goikhman wrote:
> > > >On 30 Nov 2002 15:52:05 +0100, Tor Stormwall wrote:
> > > does outline move have to grab X? it seems like most evil thing (in
> > > context given context:-), turning nice multitasking system into a one
> > > task dos piece of crap, even if it's for few moments only (mostly).
> >
> > The reason is mainly backward compatibility. We could also draw
> > the wire frame into separate windows and fill it with a pattern
> > that gives a good contrast. But we could not have the current
> > "Xor" effect.
>
> :-) considering how ugly the xor effect looks it funny that it's (part
> of) a reason why the nasty grab X is used by fvwm

Well, it is considerably faster too and does not cause any redraws
on below windows. A non grabbing implementation of wire frame
move is about as slow as opaque moving.

> > Personally I wonder
> > why people want manual placement at all. I think it is a big
> > nuisance.
>
> yes it is but why wouldn't it use opaque window when given window
> qualifies for opaque move?

It's the choice of the user. And of course wire frame operations
are still common for resizing.

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 Mon Dec 02 2002 - 10:58:21 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:54 BST