STR #2773: window always show on the wrong screen

STR #2773

Application:	FLTK Library
Status:	2 - Closed w/o Resolution
Priority:	2 - Low, e.g. a documentation error or undocumented side-effect
Scope:	2 - Specific to an operating system
Subsystem:	X11
Summary:	window always show on the wrong screen
Version:	1.3-current
Created By:	higuita
Assigned To:	ianmacarthur
Fix Version:	1.3-current
Update Notification:	Receive EMails Don't Receive EMails

Trouble Report Files:

No files

Trouble Report Comments:

#1	higuita 18:32 Nov 16, 2011

when using dillo with tabs, when closing it will show a popup requesting permission to close. this popup is configures to show on one screen, but always show up on the other screen. i'm using fltk 1.3 svn 9180 and dillo3, hg version d35a120ef07b. my window manager is the fluxbox 1.3.2 and i use 2 screens, where my main screen is the righ one. in the past, it worked fine, so i bisect dillo and found that dillo changeset 2104:4ea703ed7f15 (http://hg.dillo.org/dillo/rev/4ea703ed7f15) made the windows "locked" in my left screen. reverting it i can control the window placement. the problem is that dillo have other window like that and dont have that problem. also, running the fltk tests i dont see that problem in any of then. i have posted more info to the dillo list: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-August/008755.html http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-September/008858.html but nothing else useful was found... so i'm trying if the problem comes from fltk side

#2	ianmacarthur 14:21 Dec 22, 2011

Any update on this? I know Manolo did a pile of good work in sorting out how the screen and work areas are computed, but I wonder if the effect you are seeing might be a side-effect of that in some way? Don't know what rev Manolo's changes went in at, be interesting to see if the overlap the range you se the "feature" appearing in...

#3	ianmacarthur 16:24 Mar 11, 2014

Any further updates on this, or is this something we can close?

#4	ianmacarthur 03:36 Sep 05, 2014

There has been no more feedback on this issue, nor related reports, for some time (well, about 3 years) so I'm inclined to close for now. If there's still fault, please re-open.