After closing a tab, another open tab becomes visible, but will not accept input

After closing a tab, another open tab becomes visible, but will not accept input

avatar

This one is easy to reproduce unless it just happens to be my particular mix of settings:

1. Open a remote desktop tab
2. Open another remote desktop tab
3. Close the second remote desktop tab
4. Try clicking something in the first remote desktop session which has now become visible

The problem seems to be that the tab becomes visible, but does not have focus. If I press up or down on the keyboard, I see that the navigation pane on the left has focus. The only way to fix it is to click on the tab header to give it focus again.

I am using Remote Desktop Manager Free Version 4.0.4.0 on Windows 7 and Windows 10 computers.

Thank you!

All Comments (4)

avatar

Hello,

Indeed if you close the second one and the first one becomes visible, you need to set the focus on it to be able to interact with it.

Do you want to be able to control this with the keyboard instead of the Mouse?


Best regards,

Mark Beausejour

avatar

I think the tab that becomes visible should receive focus by default. I think the majority of users would instinctively expect to be able to interact with the session if it is visible. I thought the software was locked up the first few times it happened and ended up restarting the application. I then realized it was just the tab that was frozen and I could fix it by closing the tab and reconnecting. Eventually I realized that it was a focus issue and I just had to click on the tab header. But it is still an annoyance.

Thanks for the quick reply.

avatar

Hi,
I will check if we can automate the focus to the tab content. The problem is that sometime it could steal the focus when a tab is closed by a disconnect and will the opposite effect that you want.

Regards

David Hervieux

avatar

Actually, disconnections currently cause worse issues. If I have 3 tabs open and one gets disconnected, the rightmost tab will become visible even I'm actively working in another one. The now-visible session also suffers from the issue of not accepting input.