Session docking not working while logged in on teamviewer account

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run teamviewer
2. Open Computers & Contacts and login to your account
4. Run SuperPutty
5. Open a new session

What is the expected output? What do you see instead?

The new putty session is opened in a new window . It should have apeared as a 
docked tab in superPutty.

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

SuperPutty 1.4.0.2
Windows8 64bit

Please provide any additional information below.

If you disconnect from your teamviewer account, the new sessions apear docked 
even without restarting superputty.

Original issue reported on code.google.com by vasi...@vatsos.gr on 26 Mar 2013 at 10:43

Attachments:

• SuperPuTTY.20130326_123714.log

[GoogleCodeExporter]

It could be that when team viewer is running it slows down the computer and the 
new window doesn't spawn in time for superputty to grab it. I've seen other 
programs (I think it was putty connection manager) handle this by having a 
setting to adjust the amount of time to wait for the window to appear. I had to 
adjust the setting as my kitty windows take a long time to spawn and kept 
appearing as a separate window. I looked for a similar setting in superputty 
but couldn't find it. Being that this is active project, it would be great to 
see this setting added if it'll fix this problem. Thanks.

Thanks

Original comment by chingo...@gmail.com on 20 Apr 2013 at 6:50

[GoogleCodeExporter]

Thanks for reporting this problem. 
Now I can also pinpoint Teamviewer as the source of this issue in my case. 

It's interesting to see that you only need to login into your Teamviewer 
account to make is issue appear. No active remote session is needed.

Original comment by phil....@gmail.com on 21 Apr 2013 at 5:52

[GoogleCodeExporter]

There's a setting that should be active to have superputty wait in a loop for 
10 seconds to try to grab the putty window.

The setting is:
<add key="SuperPuTTY.LoopWaitForHandle" value="True" />

It should log something like this at WARN level:
"Unable to get handle for process on first try..."

Can you look for that log statement in your logs?  If it is and it's taking 
longer than 10s (wow), I can make that into an app config so you can play with 
it.

Original comment by btatey...@gmail.com on 29 Apr 2013 at 12:57

[GoogleCodeExporter]

I verified that the LoopWaitForHandle setting was already there and tried it 
again. Oddly it's working properly now. I'm also logged into teamviewer as 
well. I'll keep playing with it and see if it happens again.

Original comment by chingo...@gmail.com on 30 Apr 2013 at 5:33

[GoogleCodeExporter]

This issue is being caused by TeamViewer's QuickConnect feature that adds an 
additional button to every windows toolbar for easy sharing.
Adding putty.exe to exception list under the advanced settings solves the 
problem for me. 

Original comment by phil....@gmail.com on 1 May 2013 at 6:57

[GoogleCodeExporter]

Thanks Phil. That seemed to fix it for me as well.

Original comment by chingo...@gmail.com on 16 May 2013 at 5:19

[GoogleCodeExporter]

Thanks for debugging this.

I've added it to the documentation page.

Original comment by btatey...@gmail.com on 22 May 2013 at 5:07

• Changed state: Done

[GoogleCodeExporter]

The QuickConnect fix worked for me, Thanks.

Original comment by lopez.xt...@gmail.com on 1 Apr 2014 at 7:00

[GoogleCodeExporter]

teamvewer.exe>extras>options>show advance options>advanced settings for 
computers and contacts>quick connect button>configure>type putty.exe on the 
box>add>ok

Original comment by yvo...@yahoo.com on 26 Oct 2014 at 11:41

[GoogleCodeExporter]

Just ran into this problem. Fantastic solution guys. Thanks!

Original comment by joshua.g...@gmail.com on 26 Dec 2014 at 4:59

[GoogleCodeExporter]

Thank You for still keeping this up. I ran into this problem and was able to 
find the solution quick and easy!

Original comment by mrvagh...@gmail.com on 24 Mar 2015 at 2:35

[GoogleCodeExporter]

Thanks guys. Adding putty.exe to the exception on TeamViewer's QuickConnect 
resolved this for me too. 

Original comment by fats...@gmail.com on 24 Apr 2015 at 1:32