On Mon, 15 Nov 1999, Dominik Vogt wrote:
> On Sun, Nov 14, 1999 at 08:27:14PM +0200, Sampo Niskanen wrote:
> > - An old version (1.x I believe) with smartplacement set the first window
> > on a screen at position 0x0, the newer versions set it at 1x1. This I find
> > very irritating, as I can't just "throw" my cursor to the upper left and
> > get focus into the xterm there (my focus follows the mouse. I don't want
> > to use SloppyFocus). Is it possible to get fvwm not to leave these
> > empty-spaces?
>
> Which version are you using? There was a similar bug in the code for a few
> days recently, but you had had to access CVS to get this.
Sorry, I'm using version 2.2.2 (coming along with Slackware 7.0, but the
same thing was also with an older fvwm2 version). Don't get me wrong: in
my opinion the windows should be set exactly on the border, the first one
at 0x0. Of course, somebody might like spaces between the windows and
borders, but I find it irritating.
> > - In an older version there was a "bug" that when sliding the mouse cursor
> > on the top of a window left or right (over the border) fvwm didn't scroll
> > to the next page (You had to move it at least one pixel down so that it
> > scrolled. The same was with the bottom edge. This, of course, only worked
> > on the upper page). It has, evidently, been fixed in a newer release, but
> > I find myself missing it. This would be nice so you could "throw" your
> > mouse northwest as I described previously on other pages than the leftmost
> > too.
> Duh. How did you move back into the page if you didn't want to
> flip pages?
Oops. I meant "...on the top of a page...", not window. I don't quite
understand your question, perhapse you misunderstood my explanation also
(I realize it might be a bit confusing).
I use an EdgeResistance of 0 and EdgeScroll of 100 100. On the older
version (2.2.2 is the first one I've missed it. On an older fvwm2 it was
still there) when you slid the mouse cursor on the top (pixel 0) of a page
(a top page, otherwise it would have scrolled up) to the edge, it didn't
scroll (sideways). You had to move the cursor at least one pixel down
(pixel 1) to get it to scroll. Otherwise the scrolling worked fine.
What I suggest is a configurable option how many pixels around the corners
of the screen are "deactivated" from page flipping. It may sound like a
strange request, but I find it quite useful. Then again, it might not be
good for the corners where a page is diagonally located (the cursor would
get trapped in it when trying to move there). In that case you couldn't
slide it along the border to the corner anyway.
This version (I have not noticed it on any other) also seems to have a bug
conserning window movement. If you grab a window whilst moving the cursor
the window lags behind the cursor quite badly.
If, for example, you grab a window while moving the mouse up and then stop
the mouse, the window moves less so that there are 10-100 pixels between
the cursor and the titlebar. The faster you move the mouse, the more space
it lags. I have only noticed it in function with Move as the Motion ("M")
-action. It seems like fvwm "forgets" the movement that the mouse already
has moved at the point when it activates the Motion-action (Move) and
starts moving the window.
__________________________________________________
/____\ Sampo Niskanen <=> sampo.niskanen_at_iki.fi \
\
http://www.iki.fi/sampo.niskanen \
\ ___________________________________________
___/___________________________________________/
--
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 Thu Nov 18 1999 - 11:28:33 GMT