AutoHotkey Community

[MisterW]

I'm having trouble getting hotkeys to work using windows (xp) remote desktop client.

Actually (just testing...) They do work but not in fullscreen mode (which is how I tend to work, via a second monitor).

Is there a way to get this working?

Just to clarify, I'm not trying to send hotkeys on the remote machine but just to get them to respond while remote desktop is the active window (in fullscreen mode).

[Chris]

You could try adding the line #UseHook above the definitions of the hotkeys you want to be active. This might allow your client PC to catch the keystrokes (and thus fire the hotkeys) before they get routed to the remote PC.

[MisterW]

[Chris]

You've probably thought of this, but the only idea I have left is to run some or all of your hotkeys in a script on the remote machine. In fact, you might be able to have the same script running both remotely and locally so that the hotkeys are the same whether you're running in windowed or full-screen mode.

When I use Remote Desktop, I leave the script running only on the remote machine and always keep the client in full-screen mode. This allows most of my hotkeys to work, though of course they don't work on the machine running the client.

[MisterW]

[Chris]

[xx3nvyxx]

What about controlsend? Maybe the keys aren't going to the right window. :\
_________________
Now the world has gone to bed,
Darkness won't engulf my head,
I can see by infra-red,
How I hate the night.

Now I lay me down to sleep,
Try to count electric sheep,
Sweet dream wishes you can keep,
How I hate the night.

[MisterW]

[Jerry]

I just had the problem of the "remote" session (remote desktop) not receiving the keys from autohotkey. The script I have is. When the remote desktop window is open and I press LWin , then the remote session should be minimized.

I have the setting of enable windows key combinations on "fullscreen mode only"

The result would be that the windows key would activate the start menu (on the remote session only)


By experimenting I found out you can solve the problem 3 ways.

1)
a) #usehook must be used (I only needed this command for the letter 'z')
b) the hotkeys must be dynamic
See script below.

2) Start the script after the remote desktop session has started so it get the hook first.

3) You could also keep 'reload'ing the script too.

My guess is that the RDP client window grabs the key first and then hides it from the local machine, like the way autohotkey does. Not sure if this is completly correct but the idea works.

Chris - If your think its worth it, you could add a command to reload / reaquire all hotkeys/hotstrings/etc in a script.

Here is the script

[Chris]

Thanks for posting your findings. They'll be valuable to me and others.

[vijucat]

Restarting AHK on the local machine after initiating Remote Desktop worked well for me. However, AHK is now running on both machines so I'm not sure which one is picking up the messages!