Quote Originally Posted by 'Souca',index.php?page=Thread&postID=135916#post13 5916
In what manner does IS interact with the WoW client? Does it behave as a DirectInput device to send key or mouse clicks? Does it have access to any client memory? Can an addon running in WoW communicate with IS, which I assume is running external to the client and not as a addon, and can IS send info back to that addon in a manner other than keystrokes or mouse clicks? When multiboxing with IS, you mention clicking a in game UI button which then triggers actions on other clients; how is that message sent to the other clients?

Sorry for the specific technical questions, but like Xzin, I want to understand how IS works.

- Souca -
Inner Space runs inside the client's memory space (the name Inner Space is meant to hint at this). It interacts by providing a layer between the game, and Windows. All input systems used by games are virtualized by Inner Space and combined into a single interface, so that regardless of what input system the game is using (DirectInput, win32, etc), it should simply work. There are bugs sometimes with the virtualized input system, so some games the input does not seem to work -- this is pretty rare but is the most common reason for Inner Space not being compatible with a given game. For example, I just heard recently that Battlefield 2 seems to have this problem. When I find out about bugs like this, I usually try to get them solved as soon as possible. With the virtualized input system, Inner Space is actually processing all of the input the game receives, before the game receives it, and any keys or mouse clicks to be emulated are simply input into the stream as if it were actually pressed.

The message being sent to other clients is sent via Inter-Process Communication to another Inner Space session (e.g. an instance of WoW using Inner Space), which can use the system described above to emulate keystrokes or mouse clicks. If the session is on a remote PC, the message is sent via TCP between the Uplinks (what the IS main program is called) as long as they are networked (disabled by default). When you click on a ClickBoxer button, it executes a command like so:
Code:
relay all press alt+f
"relay" in this case is the name of a command which can pass another command to one or more sessions. In this case, it is being sent to "all", which means all sessions but the one relayed from. The command being passed is press, with a parameter alt+f, which as I probably don't need to explain, presses alt+f. There are a lot of other commands, and more than one command could be executed per button press if you really wanted, but the typical deal is "one key to one action", so ClickBoxer sticks to that in its sample form. It is up to the user to remain within the rules.

I don't know the answer to legitimately communicating with WoW add-ons. The only communication with add-ons that I know of happening was through ISXWoW, and that falls outside of what we want to be discussing. However, I would LIKE to be able to legitimately communicate with WoW add-ons, in order to improve functionality of, say, the Ventrilo interface for example: if it's possible to do without raising flags, I would like to make it a one-click no-typing deal in order to join a Ventrilo server for a pre-made battleground, by having an addon transmit the server details to my application. I will admit I don't know enough about the capabilities of WoW addons in particular to answer this question properly.