Alanaktion / transmisson-remote-gui

Automatically exported from code.google.com/p/transmisson-remote-gui
GNU General Public License v2.0
1 stars 0 forks source link

Maximising transmission-gui not working #274

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Having about 250 or more torrents running on the remote server / or just
enough for the remote machine to have high delay responding
2.Launching transmission-gui
3.

What is the expected output? What do you see instead?
After launching transmission-gui, it goes into tray.
Double clicking on it put it into the taskbar.
Problem come here : clicking on it in the taskbar to maximise just
put it into tray again without maximising it.

If I just rollover the tray icon, i can see upload/dl speed and 
number of torrents seeding/leeching so it's not a connection issue.

What version of the product are you using? On what operating system?

I'm using 2.0 stable of transmission-gui, on windows 7 x64.

Please provide any additional information below.

My transmission client is 1.92 ( latest supported by my tracker )
transmission client runs on linux nas ( modded linux based on centos )
cpu load of transmission client is 30% average / got free ram , free 
diskspace
I can manage transmission via the web interface, but with high delay.
I think maybe it's a timeout issue for the gui.

Thanks for looking into it.
Michael.

Original issue reported on code.google.com by kryptonaute@gmail.com on 23 Aug 2010 at 8:33

GoogleCodeExporter commented 9 years ago
Probably you have the main program's window on a secondary monitor.

Original comment by j...@cp-lab.com on 23 Aug 2010 at 8:50

GoogleCodeExporter commented 9 years ago
How can i check that ? I don't have a second monitor enabled.
I've justed removed 30 torrents with the web interface, and transmission-gui
works fine now without further windows configuration.
thx.

Original comment by kryptonaute@gmail.com on 23 Aug 2010 at 9:09

GoogleCodeExporter commented 9 years ago
Then it is not a secondary monitor issue. 
If it will happen again please report here. I am closing this issue for the 
time being.

Original comment by j...@cp-lab.com on 23 Aug 2010 at 10:57