linuxdcpp-team team mailing list archive

[Steven Sheehy <610248@xxxxxxxxxxxxxxxxxx>]

I agree, it should be fixed. gdk_screen_get_primary_monitor() is brand
new in GTK+ 2.20 and since we support down to 2.10, it can't be used
directly. However, I will accept a patch with #if GTK_CHECK_VERSION (2,
20, 1) around the function. Since I don't have a dual monitor setup I
can't really fix/test it myself.

About the get pos/size functions returning junk, that was there because
they literally did return junk at one point. That is, they didn't return
values in the range [0, screen_size] when the window was maximized.
However, looking at it now it seems GTK+ must've fixed the bug that
caused that and it returns valid values now. The problem with saving the
maximized value is that when you unmaximize your window it doesn't go
back to the size you had before it was maximized. In fact, it stays at a
size almost the same as the maximized window, making it seems as if the
unmaximize button didn't function properly.

If you have an issue with it not showing up on the correct monitor I say
we fix that instead of trying to workaround the issue by saving the
maximized values to help for your specific case. That's my opinion at
least.

** Changed in: linuxdcpp
   Importance: Undecided => Medium

** Changed in: linuxdcpp
       Status: New => Confirmed

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