RDM 11.7.2.0 (32&64) Keeps falling behind other maximized windows
RDM 11.7.2.0 (32&64) Keeps falling behind other maximized windows
It appears that randomly RDM maintians input focus but falls behind other maximized windows that are behind it. Clicking on RDM in the taskbar causes it to minimize as it still has focus. This is with "Always on top" disabled.
A similar issue that is probably related is the context menus disappear. Right click on an element in the tree view and often enough the context menu will disappear making you have to try right clicking 2 or 3 times to get the menu to stay.
This happens on multiple systems running Windows 10.
All Comments (8)
Hello,
This is very strange.
Could you post a small video of the issue so that I can try to reproduce it in our environment.
Best regards,
Jeff Dagenais
I have sent an e-mail to support containing this link and the video requested.
Hello,
Thank you for the video (I have attached it to my post).
I am not able to see the issue mentioned in your first post in the video. In the video, we see that opening a LogMeIn session takes a few seconds.
Is this the issue?
Best regards,
Jeff Dagenais
MichaelBazdell.mp4
In the last second of the video you see the screen switch to Excel, which is open behind RDM. Due to sensitive information, I had to keep the video short unfortunately.
I assumed opening LogMeIn sessions making RDM "Not Responding" for a few seconds was due to how RDM works and can't be fixed. Is that a bug too? It would be fantastic if it stopped doing that.
Hello,
Ok, so you don't click on anything and the focus switch to Excel by himself? This is strange, I will try to reproduce on my computer.
For the opening of your LogMeIn sessions, do you have the Sandbox process and embedded 32 debug mode options checked in the properties of your LogMeIn sessions? With both options enabled, sessions may be slower to start.
Best regards,
Jeff Dagenais
That's exactly what it's doing. Doesn't matter if it's Excel, Chrome, or any other window.
I only had the Sandbox process enabled. I disabled that and it is indeed much faster.
I believe this is only an issue when LogMeIn sessions are sandbox'd. I've ran it for the last 2 days disabled and haven't had it happen since. However, due to a keyboard input bug with LogMeIn not being sandbox'd, I need to sandbox the connections.
Hi Michael,
Thank you for those details. We will try to reproduce your issue in our environment with the help of our QA team.
Best regards,
Jeff Dagenais