xwininfo -root xwininfo: Window id: 0x89 (the root window) (has no name)
Absolute upper-left X: 0 Absolute upper-left Y: 0 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 3200 Height: 1200 Depth: 24 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x20 (installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +0+0 -0+0 -0-0 +0-0 -geometry 3200x1200+0+0 The video driver actually reports the combined size of 3200 so as far as X is concenred it is just one wide screen. On Thu, Dec 19, 2002 at 05:59:59PM +0100, Dominik Vogt wrote: > On Thu, Dec 19, 2002 at 11:43:17AM -0500, Brad Giaccio wrote: > > Well I seem to have confused fvwm I just got a video card that supports > > to monitors as one screen. > > > > Fvwm and a 3200 geometry are very confused. Most notablly when I drag > > a window from montior one to the second I can watch the x coord go up > > until I get to 1600 and then it resets to zero. this really brakes > > things like the initail placement of FvwmButtons at -0+0 it winds up at > > 1600+0. but if i place it where I expect it to be and use FvwmIdent I > > get correct screen coordinates in the 3thousandths. > > > > I doubt anyone has the setup to reproduce this but its been a while > > since I've done editing and I know you've made substantial event code > > changes so some pointers would be helpful. > > I rather guess the video card confuses the X server. If what I > understand is correct, fvwm is not even aware of the second screen > (unless you use Xinerama or dual head). That sounds as if the > display width is only 1600, not 3200. What does > > $ xwininfo -root > > say? > > Bye > > Dominik ^_^ ^_^ -- --- There are two kinds of knowledge, you either know the answer or you know where to find it -Kane, Johnson, and anonymous -- 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]