On Thu, Jun 15, 2006 at 09:30:17AM +0200, Dominik Vogt wrote:
> It actually wasn't this bad. The idea behing the test in the
> ButtonReleasee handler was to make sure the window is snapped if
> the window did not move before, but the pointer position in the
> release event moved the window.
>
> I
On Tue, May 30, 2006 at 11:11:11PM +0200, Dominik Vogt wrote:
> On Mon, May 29, 2006 at 02:27:15PM -0700, Andrew Pimlott wrote:
> > To resolve this issue, we must 1. decide whether the outline should
> > initially appear snapped or unsnapped;
>
> Unsnapped. In case of moving
I have been bothered by a situation where I create a window and manually
place it at one location, but the window actually appears in a different
location. It is easy to reproduce with a very small .fvwm2rc:
Style * ManualPlacement
EdgeResistance 0 100
Start by placing an xterm in the lo
The ManualPlacement documentation says that if you hit Escape during
manual placement, the window is put in the top left corner of the
screen. That was true in old (2.2?) FVWMs, but for some time it has
actually put the window at (-1, -1), ie one pixel off the upper left.
The following fixes this,
I was using the fvwm distributed in the Debian Testing distribution (based
on 2.2.5), and I noticed that if the configuration had two
*FwwmPagerGeometry settings (eg, one in the system config file, one in the
user config file), they would interfere with each other. For example, the
default /etc/X1
