or ALL_REMOTE to go with "local" (and maybe ALL too)...
I'm not sure whether I can do this because the program allows people to specify an IP for the local PC. Hotkeys get "expanded" -- undergo quite a bit of text substitution -- at the time the program loads them. In a case like this, the loader wouldn't realize that the local IP is local and not remote. If I were writing the program from scratch I could have handled this, but at this point, it might involve more work than I want to do. I'll have to look at the source code and see how much work it would be.
Also the UI select which IP the server should be listening from and its definition of itself (for multiple network interfaces cases)
Do you mean your server has multiple IPs and you need to tell the server copy of HotkeyNet which IP to listen with?
Edit: I don't have multiple IPs here so I can't test, but the program is written in such a way that the server is supposed to listen on all its IPs, so you should be able to control this now by entering whichever server IP you want to use in the client copies of HotkeyNet. Is it not working that way?
By the way, in case you don't know, you can send commands from any copy of HotkeyNet to any of the others regardless of which one is the server and which are clients. You can designate some other machine to be the server if that helps.
Connect With Us