AutoHotkey Community

[Akize]

To be more specific, on the host computer Active Window Info will always report:

[engunneer]

I'm not sure what you mean. The remote computer has some hotkeys on it that are working right, even though (locally) you only see this particular ClassNN? that is not a bug at all. If you open Window Spy on the remote computer, you should see all the correct window names. On the local computer, you will only see the window which is effectively a screenshot of the remote computer, even though the local computer is rendering most of it.

This seems normal to me.
_________________
Unless otherwise noted, all code is untested.
Common Answers: 1.(Loops, Viruses, etc.) 2. Search 3.RTFM

[Akize]

Local computer is running a script, remote computer is running nothing. Let's say I bound ^q to !f4 for Firefox.

The hotkey works locally, and then it works remotely even though the active window info is reporting the Remote Desktop class.

I haven't tested this out but it'd be interesting to see if you had two scripts running (one on remote, other on local) which one takes preference.

[engunneer]

local should always take the key, unless the ~ option is used. I'll have to test your results with another computer I use when I get home. Sounds interesting.

I wonder - is it possible to get conflicting windows this way? maybe have an untitled - Notepad open on each PC?
_________________
Unless otherwise noted, all code is untested.
Common Answers: 1.(Loops, Viruses, etc.) 2. Search 3.RTFM

[Chris]

I seem to remember that Window Spy uses the equivalent of "SetTitleMatchMode Fast" (i.e. AutoHotkey's default mode). Therefore, if your script uses "SetTitleMatchMode Slow" in the auto-execute section, that might explain the difference in behavior.