SuperPutty gets in bad state and blocks Windows shortcuts, such as Alt+Tab

[GoogleCodeExporter]

Problem description: Alt+tab Windows shortcut does nothing, i.e. the screen 
continues displaying the same app

What steps will reproduce the problem?
The steps are not clear. All I know is that I had several tabs opened in 
SuperPutty and I undocked my laptop at work and brought it home. When at home I 
tried to Alt+Tab from my current window to SuperPutty and wasn't able to. I 
killed and restarted explorer.exe but that didn't help. I Googled for "windows 
7 alt tab stopped working" but none of the advice worked. However, somebody 
suggested restarting some Windows service which managed Windows Desktop, which 
I did without any result. I finally killed superputty.exe and my alt+tab keys 
started working. 

What is the expected output? What do you see instead?
Alt+tab should switch tabs. Instead nothing visible happened

What version of the product are you using? On what operating system?
SuperPutty 1.4.0.3. Windows 7 Pro 64bit

Please provide any additional information below.
Please see above

Original issue reported on code.google.com by alecs...@gmail.com on 21 Mar 2014 at 1:33

[GoogleCodeExporter]

I have a similar problem. Everything is working fine and after some hours or 
days, all the shortcuts are not working anymore. I'm using superputty also at 
work with several login/logout times every day. Normally the login/logout 
doesn't affect but perhaps the problem is related to that.
I've tried different configurations of "Activators" but I could not find a 
solution to this problem. The only way to overcame the problem is to restart 
superputty.

I have this problem with 1.4.0.4 and also with 1.3.0.7 (Windows 7, 64 bits)

If I press any of the function keys (e.g. F2) a "~" character is printed out to 
putty. <ctrl-tab> is not working at all.

I would be happy with a solution or at least a workaround to at least not lose 
the active putty connections. Superputty is the best putty manager I've ever 
used, congratulations and many thanks for developing it!

Can I send you have any log? I will leave the log viewer opened for the next 
time

Original comment by damg...@gmail.com on 27 Mar 2014 at 9:52

[GoogleCodeExporter]

More info:

I'm using this configuration:

[ ] Enable Control-Tab Tab switching
[x] control-tab window switching
focus activator: KeyEventWindowActivator

When I start superputty for the first time, <ctrl-tab> is working but quite 
slow and the focus remains in the previous tab. I found a workaround for that: 

- start superputty, go to configuration and enable tab switching:
- [x] Enable Control-Tab Tab switching
- [ok]
- then disable it again:
- [ ] Enable Control-Tab Tab switching
- [ok]

After that superputty works properly.

But unfortunately this workaround does not solve the shortcut problem described 
in this issue (above).

Original comment by damg...@gmail.com on 27 Mar 2014 at 11:08

[GoogleCodeExporter]

I have the issue today again. I had the log viewer running. The problem was 
between 11 am and 1 pm at 2014-03-28 (I can not say exactly the time). I see 
this suspect lines in log:

2014-03-28 11:22:44,873 WARN         DesktopWindow - Could not get exe.  
error=Access is denied, process=8348
2014-03-28 11:22:44,875 WARN         DesktopWindow - Could not get exe.  
error=Access is denied, process=8348
2014-03-28 11:27:38,689 WARN         DesktopWindow - Could not get exe.  
error=Access is denied, process=8348

After that the shortcuts are not working anymore.

The whole log is attached. If you need more info, please let me know.

Original comment by damg...@gmail.com on 31 Mar 2014 at 12:20

Attachments:

• superputty_shortcut_broken.txt

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The problem still exists with version 1.4.0.7. Please fix this bug. It's 
annoying losing the ctrl-tab feature since the only solution is to restart 
superputty.

I've found this patch:
- http://superputty.googlecode.com/svn/trunk/Patches/Shoutcut.patch

Is it related to this problem?

Original comment by damg...@gmail.com on 11 May 2015 at 9:40