Quote Originally Posted by 'skarlot',index.php?page=Thread&postID=74263#post7 4263
I can't give any information, at this point. Other than you do need to DLL inject, which is pretty obvious.
Thanks for providing some info about this. Like you said the other day, this is a fun puzzle, and you and I might be the only two people in the history of the universe who have tried to do this with WoW in software. So naturally I want to talk about it!

The way I did this was simply by moving the cursor with ordinary system calls (SetCursorPos in the Win32 API) and then sending a WM button-down/up messages to WoW. Nothing the least bit hackerish. Just straightforward stuff. This works regardless of whether WoW has the focus or not. However if WoW doesn't have the focus, there has be be a delay (something on the order of 6 to 30 ms depending on the PC's speed etc.) between moving the cursor and sending the message. So the question for me is, what can I do to update WoW's source of location info faster. If I knew where it's looking for that info, maybe I could figure out a way.

I'm guessing that you know where and how WoW is getting its cursor location info from hooking the DLL, and I would sure love to know that. I don't want to hook any DLLs myself -- that's not the kind of thing I would do with HotkeyNet. But knowing exactly what you do while you're in their address space (what you change or intercept or read) would be useful to know.

The no click's in the background thing is the result of default window behaviour on WoW's part. To circumvent it you gotta subclass it
I'm not sure what you mean but like I said, you can simply send WoW a button-down message while it's in the background and it processes it just fine.

Quote Originally Posted by Xzin
Heh, hardware boxing lets you do this already.
When the windows are different sizes? When they are covered by other windows? When the windows are in the background? Software can do all those things. This calls for a flex emote but I don't see one!