linuxdcpp-team team mailing list archive

[Francois Botha <610248@xxxxxxxxxxxxxxxxxx>]

>From the GtkWindow documentation:

If you are saving and restoring your application's window positions, you
should know that it's impossible for applications to do this without
getting it somewhat wrong because applications do not have sufficient
knowledge of window manager state. The Correct Mechanism is to support
the session management protocol (see the "GnomeClient" object in the
GNOME libraries for example) and allow the window manager to save your
window sizes and positions.

Don't know where I got the idea that the window state is automatically
saved by the window manager.

-- 
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.