Quote Originally Posted by ElectronDF View Post
I am one of the multiple computer boxers (lots of people box on one computer). I would have to have network support.
I would like, if you are too awesome to have a mixed PC/Mac support. But I don't need all the bells and whistles. I don't need multiple windows on a computer, I don't need macro integration, I don't need any sandboxing or CPU/GPU options. For the Mac/PC part, I would just need to have the Macs receive keys.

Now that Blizzard has changed WOW to not do round robins, I have to do that outside in my key broadcasting software. I use HotKeyNet. That would be pretty important.
It has been nice to start WOW on the other machines through a keystroke. I guess being able to run a shell/command line command would be nice.
It would be good to have a way to see, 1) What key sequence did you push "You last pressed: CTRL-ALT-G", 2) Did that sequence get sent to other computers/windows, "Computer 2 received your keys", "Window WOW2 was not available", 3) Be able to not blow up if a computer/window is not running (like if only 2 out of computers/windows used).
For networked computers, be able to use computer name instead of IP address (in case of DHCP).
For mice, support for button4/5 (thumb buttons on side of mouse). I don't really require click broadcasting. I know others would want it bad. But I would require button broadcasting.

I have used HotKeyNet since the beginning. I really like the programmer. Great support, nice forum for support (here and there). I like that it is free. I like that there were features added. I would suggest starting off small and work your way up. For me, something working is better than promises. I really only box in WOW.
I'd love to put this on a Mac, as well, but I do not own one (nor the funds to get one), and then I'd have to learn how Macs do windowing and input, since right now I'm using WinApi libraries. So I don't see that being a foreseeable possibility, unless someone wants to send me a Mac (or I can somehow legally use Mac in a virtual machine?)

As for round robins, that was already going to be a feature from the start, as well as launching the game window. I have an old program that I made for myself to manage my multiple accounts before the inclusion of Battle.net being tied to one email (it automatically opened the game, input my account/password in 2-channel obfuscated fashion, etc. So I have some code for that already built.)

Verbose event logging is already in the basic client (state changes, keystrokes, etc), and I plan on making it a lot nicer (Sorting by message type, some richtext formatting, etc)

Hostname support is already included with the networking library, so no worries with DHCP and having to fiddle with your IP address. (Did I also mention that communications across the wire will be encrypted with a shared password and AES, for your security?)

I'm debating on whether or not to release the basic client (Just simple networked keystroke cloning), as a start-up point, and then release further updates as I add features, or have a number of requested features in before releasing, eh community?

I'm really excited about the feedback, thanks a lot guys, you've given me a lot to do, and it's really fun!

While working on some code for one of the features, I started a side-project, whipped it up in short amount of time last night, to make windows borderless. I made another post about this in this forum topic, so check it out! (If you wanted/needed borderless windows, that is, I believe a lot of solutions already do this).