Bug? (Re: FVWM: NearestEdgeResizing)

From: Gert Brinkmann <g111_at_netcologne.de>
Date: Wed, 05 May 2004 10:13:25 +0200

Mikhael Goikhman wrote:

> This first example works like you want. But the following second example
> requires mouse release (and then Resize requires mouse click, since we
> are not dragging anymore):
>
> DestroyFunc MyResize
> AddToFunc MyResize
> + I PipeRead `echo WarpToWindow 100 100`
> + I Resize
>
> Seems like a bug, because the following works without additional mouse
> release and click:
>
> DestroyFunc MyResize
> AddToFunc MyResize
> + I PipeRead `echo Echo just to have some command executed`
> + I WarpToWindow 100 100
> + I Resize
>
> I think this should be fixed, but let's wait for the Dominik's reply.

Just to point attention to this: Is it a bug, Dominik?

btw: I have found that my solution does not work reliable. When moving
the mousepointer to fast, resizing often starts to late after the
mousewarping so that the mouse pointer is no longer on the window's
corner and you have to move the mouse back to it. The higher the load of
my slow machine, the more often this happens.

It would be good to change the order of the commands. First "Resize" and
then "WarpToWindow", but "Resize" must not block then. I think this is
not possible.

So it would be great if someone could implement this in fvwm sometime.

Thank you,

Gert
--
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 May 05 2004 - 03:16:53 BST

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