On 22 Jul 2001 09:29:00 +0200, Dominik Vogt wrote:
> 
> On Sun, Jul 22, 2001 at 01:48:00AM +0000, Mikhael Goikhman wrote:
> > On 21 Jul 2001 14:29:27 -0500, FVWM CVS wrote:
> > > 
> > > Log message:
> > > * First version of Xinerama support.
> > 
> > I don't think that HAS_XINERAMA is ever defined (because XINERAMA_CPPFLAGS
> > is nowhere used) and thus parts of the xinerama code are ever compiled in,
> > although it is reported as such.
> 
> I don't know.  At least for my Xinerama setup it works: the
> Xinerama code is compiled in.  The code in configure.in sure looks
> different.  Shouldn't this HAS_XINERAMA macro end up in config.h?
> Perhaps this would be a good practice for me to learn writing
> configure code.

Do you say you ever got "Xinerama" in "fvwm -version"? I don't think so.

You almost fixed it on the second commit, but did a typo
s/XINERAMA/HAVE_XINERAMA/. Also building of libfvwm.a failed, because
-lXinerama was not passed to it.

Now it should work.

> > It is also buggy. Windows get Y coordinate -99999, i.e. disappear, when
> > trying to move them...
> 
> I don't have this problem.  Was Xinerama support compiled in?
> Can you have a look what's happening?

Yes, Xinerama support is on after "configure; make install".
I have a single screen.

When a window is dragged (mouse moved) or a window is shaded, it gets
Y coordinate -99999.

When printing xl and yt in moveLoop() before loop or even on MotionNotify
they seem ok, although I don't understand their exact meaning yet. But on
ButtonRelease yt becomes -99999.

The window disappear when mouse is moved, not only when mouse is released.
In addition, the feedback window is not visible.

> > I don't have any real hardware xinerama setup, but X supports it.
> 
> I will add some code to simulate Xinerama on a single screen.

Ok, I may try it later, but for now I have problems without simulating
black holes on a single screen.

Regards,
Mikhael.
--
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