On Mon, Mar 18, 2002 at 08:13:30PM +0000, Mikhael Goikhman wrote:
> On 17 Mar 2002 22:49:01 +0100, Dominik Vogt wrote:
> > 
> > Apart from the apparent bugs (windowshade doesn't do anything,
> > the border layout of small windows is screwed, window corners
> > sometimes flash above the parent during opaque resizing), what do
> > you think about the now code (mostly in terms of speed, but feel
> > free to comment on other aspects too)?
> > 
> > I'm not sure because my machine is so fast, but I think opaque
> > moving and resizing is already a lot faster.  When the bugs in the
> > border layout are fixed, I'll switch to using background pixmaps
> > in the title bar too and then take a look at window shading.
> 
> I am not sure what to say. Do you mean it is finished? :)

Of course.  I have lost interest in fvwm and am going to be a zsh
hacker now ;-)

> Maximize does not place right-aligned window buttons (I guess they are
> covered by a title).
> 
> Resize (if done sharply) screws right-aligned window buttons, there is a
> small positive or negative X offset depending on sharpness.
> 
> Style xv HandleWidth 10  # or any other number
> does not update border geometries (looks terribly).
> But at least Recapture/RecaptureWindow seem to work now.
> 
> WindowShade is disabled.

This is all caused by the fact that a frame 'setup' operation can
not really be forced at the moment.  THat is one of the next
things to do.
 
> NoHandle does not work.

That's already fixed in CVS.

> Try to resize the maximized window then cancel resizing, the window is
> not maximized now as it was.

The doesn't seem to be related with the frame rewrite - and I
don't see this here anyway.

Bye

Dominik ^_^  ^_^

-- 
Dominik Vogt, email: [EMAIL PROTECTED]
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to