"Global Hotkey" is not global anymore on 2026.3.5.0. When RDM is not in focus, attributes are not copied anymore to clipboard. Very annoying...
Any help? I restarted the app and PC already but didn't change.
Recommended Answer
Hello,
I've found and fixed the issue. Shortcuts set to "Global hotkey" should properly execute even when RDM isn't in focus. You can expect this with the upcoming 2026.3.9 version.
Regards,
@Jafran Majeau
Hi Jafran
I can confirm, that the issue has been fixed on v2026.3.9. Many thanks.
Best regards
Hello,
This is most likely due to the framework our UI uses changing in the latest version which may have caused this side effect.
I will open a ticket to investigate and fix this issue. As a side note, could you let us know the specific shortcut combinations you are trying for which specific actions so we can make sure your specific case works after the fix?
Best Regards,
Michaël Beaudin
Hi,
I was using:
They were working just fine in the previous version. A quick fix would be highly appreciated.
Best regards
Michi
Hello,
This is most likely due to the framework our UI uses changing in the latest version which may have caused this side effect.
I will open a ticket to investigate and fix this issue. As a side note, could you let us know the specific shortcut combinations you are trying for which specific actions so we can make sure your specific case works after the fix?
Best Regards,
@Michael Beaudin
Same issue here. We use "Search everywhere" in the separate window (Ctrl+Space), even when RDM is not the active window. The shortcut does work when the Mode of the keyboard shortcut is changed to default, but then it only works if the RDM window is active.
Hello,
I've found and fixed the issue. Shortcuts set to "Global hotkey" should properly execute even when RDM isn't in focus. You can expect this with the upcoming 2026.3.9 version.
Regards,
Jafran Majeau
Hello,
I've found and fixed the issue. Shortcuts set to "Global hotkey" should properly execute even when RDM isn't in focus. You can expect this with the upcoming 2026.3.9 version.
Regards,
@Jafran Majeau
Hi Jafran
I can confirm, that the issue has been fixed on v2026.3.9. Many thanks.
Best regards