SuperPutty opens sessions in a new Putty Window

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Downloaded, unzipped and executed the superPutty executable
2. Linked it to putty (located in Program Files)
3. PuttyConnectionManager was running in the background (probably not related)
4. Right clicked in sessions, and created a new session
5. Started the session by double clicking on it, and a putty window opened 
along with a blank tab in SuperPutty. The blank tab was not black in color, but 
had the light blue theme that's always present.

What is the expected output? What do you see instead?
I expected to see a tab running my ssh session as depicted in screenshots

What version of the product are you using? On what operating system?
I used both 1.1.0.9 and 1.2.0.5
Windows 7

Please provide any additional information below.
None in particular

Original issue reported on code.google.com by neotaruntius on 7 May 2012 at 7:09

[GoogleCodeExporter]

Looked around - found the solution. 
Solution:
Remove hostname in your settings for putty. 
I had hostnames for all my profiles, even for my default settings. 
After removing works like a charm.

Original comment by neotaruntius on 7 May 2012 at 7:21

[GoogleCodeExporter]

Once PuTTY has been started SuperPuTTY tries to access its main window. With 
the hostname specified in the profile it takes a little longer for PuTTY's main 
window to be established.

There is code in SuperPutty to wait for the window but that uses 
m_Process.MainWindowHandle which is cached when the object is first created. An 
m_Process.Refresh() is needed to give us the handle when it comes along.

A patch is attached that does that. I've also shortened the sleep to 50ms, 
100ms seemed a little to long. On my virtual server it takes about 120ms for 
PuTTY to get going in this situation. Perhaps 20ms sleep would be even better. 
Added a diagnostic to say how long it actually took too.

Rob

Original comment by roblow...@gmail.com on 8 May 2012 at 2:26

Attachments:

• PuTTYStart.zip

[GoogleCodeExporter]

I suspect this problem maybe the same as Issue 7

Original comment by roblow...@gmail.com on 8 May 2012 at 9:04

[GoogleCodeExporter]

Issue 20 is also the same thing again. The code in issue 20 doesn't quite do 
the trick because of caching that goes on in the Process object.

Original comment by roblow...@gmail.com on 8 May 2012 at 9:19

[GoogleCodeExporter]

Issue 73 may well be fixed by this too.

Original comment by roblow...@gmail.com on 8 May 2012 at 10:12

[GoogleCodeExporter]

merged in patch...looks good.

Will be in 1.2.0.6

Original comment by btatey...@gmail.com on 9 May 2012 at 12:54

[GoogleCodeExporter]

Thank you for such a quick turnaround on this!

Original comment by neotaruntius on 9 May 2012 at 12:59

[GoogleCodeExporter]

Original comment by btatey...@gmail.com on 9 May 2012 at 10:00

• Changed state: Fixed

[GoogleCodeExporter]

Issue 7 has been merged into this issue.

Original comment by btatey...@gmail.com on 28 May 2012 at 9:46

[GoogleCodeExporter]

Issue 20 has been merged into this issue.

Original comment by btatey...@gmail.com on 28 May 2012 at 9:46

[GoogleCodeExporter]

Issue 73 has been merged into this issue.

Original comment by btatey...@gmail.com on 28 May 2012 at 9:47