linuxdcpp-team team mailing list archive

[Razzloss <razzloss@xxxxxxxxx>]

It should be up to the WM to position the window. So I'd remove the
size/position setting, at least when there's no previous values saved.
Don't know if someone wants it to remember the previous position and
restore to that no matter what (maybe make it optional?)

BTW. If the window is closed on a monitor and then that monitor is
removed will it restore itself to outside the visible area on next
startup?

-- 
Incorrect startup monitor
https://bugs.launchpad.net/bugs/610248
You received this bug notification because you are a member of LinuxDC++
Team, which is subscribed to LinuxDC++.

Status in Linux DC++: Confirmed

Bug description:
I have a dual-monitor setup with my secondary monitor on the left and primary monitor on the right.

On first startup (when LinuxDCPP.xml doesn't exist), LinuxDC++ will open at position X=100 (which is on the secondary monitor) instead of something > 1024 (primary monitor). I then have to drag it over to my primary monitor.

Also, because I immediately maximized my window (and never unmaximized it), the X position is never saved. After months of frustration I realised this only after inspecting the code myself (workaround was to unmaximize, drag over to primary and quit program so that X saved as > 1024).

I see the latest GTK has a gdk_screen_get_primary_monitory() function which could aid with this? But what is the minimum requirements in terms of GTK?

PS: To add to my frustration, my secondary monitor is actually my TV, which isn't always on. I had to switch on the TV so that I could drag the LinuxDC++ window over.