Proof of concept, multiple cursors one pc

[skarlot]

well its not proof, it could be doctored easily, and it's not quite what it may look like, it's not 4 windows cursors, but 4 WoW's without 'hardware cursors', but the code works in hardware mode also you just don't see the additional cursors. It will click simultaneously on 4 . What I havn't said is it might not get released, because it potentially moves into warden sensitive territory, which I do not want to comment on any further, unless you have precise knowledge of what Warden does/doesn't do, it is way too difficult for me to debug, I don't know where to start. But I can look at what certain other apps do (legal ones), and judge whether I think it will cause a problem based on that, and I can guinea pig my toons. I think its pretty certain the concept itself won't be bannable. . Fun little challenge!

yeh and i should prolly mention, that it will be totally off by default, definitely.

[Freddie]

Very nice. Do you feel like talking about the details or is this a trade secret?

[Ðeceased]

hehe shweet I gotta agree with freddie, would be good to see how you did it ^^ for me it's just out of curiosity ^^

[Anozireth]

How does it handle the focus of the windows? Do they all get every click without having to activate them somehow?

[skarlot]

I can't give any information, at this point. Other than you do need to DLL inject, which is pretty obvious. But that, for those who don't have any idea, is something even a program called The Governor, for monitoring Warden does, so in itself, is not a problem.

What you need to do exactly is pretty much like open sourcing it, on this occasion I am undecided if thats a good idea at all, since someone can just take my DLL and use it for a bot or something.

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, but no telling exactly what thats half the fun! The other part, I am not detailing just yet.

had to edit this cos part of it was wrong :P lol.

[Ughmahedhurtz]

Yeah, I tend to agree with your statement about others using it for malicious behavior. :P

[skarlot]

seems silly to risk it.

anyways i got it goin properly with mouse looking so its all good. course its not implemented but i've played with it to the point i know it's doable.

[Xzin]

Heh, hardware boxing lets you do this already.

[Freddie]

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.

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!

[skarlot]

well you figured out it how better than I, since I used SendInput and didn't bother with any WM_'s etc. So I found at least 20ms per window, before and after the click. Wow is using GetCursorPos but handling mouse looking is more difficult since WoW will try and use SetCursorPos on each background window and expect it to go to the centre of the desktop, so you have to be intelligent about that . Supose I can fine tune now based on this, and with SendMessage you'd be certain of WoW processing the up click straight away so you could eliminate any post-click-delay.

Well part 2 I'm just saying its possible to get it to accept a click straight from the background, direct from the mouse, which isn't neccessary since there is TweakUI and same deal in Vista but those are annoying to have running for general use. I hadn't figured out the WM messages would cause a click anyway so it was the first thing I was looking to solve.