Interbox 1.0 - software KM switch

[skarlot]

0.98 add's a couple of options for hotkeynet. I'm not offering any support in writing HKN scripts, so don't ask me how to set it up. There r some guidelines tho in the topic post now... and tool tips detail.

:sleeping:

[Spartan304]

OK, any clue what I'm doing wrong? Im running the 64 bit server on Windows Vista 64 (as an administrator) and the 32 bit client on Windows XP. I've forwarded the correct ports and type to the server machine address and the client machine will connect to the server, however the mouse movements will not transfer over. I had it set up and working fine between 2 XP machines so I'm pretty sure I have the configuration correct. Any ideas?

[skarlot]

I use it with Vista 64 ultimate and XP 32 clients.

If something were wrong with your ports, the clients would drop, and if it were UDP, at least the mouse would move to the client and then stop.

The program is pretty simple none of the options should cause any problem to stop the KM working.. thus I will need to think, but in terms of what you should expect to see on the debug log, the client will "spam" the server when at transition is detected, and the server will process it. My question would be does the client do that? and is that consistent on all sides of the screen?

[drillkid122]

does this software do the same thing with 2 wow in 1 comp?

[skarlot]

no this is absolutely no use to 1 PC.

[drillkid122]

b4 i buy it , does this work for vista 32 bit?and if i have 2 comp with 2 wow, wen i move my mouse, the other comp will also move the same thing?

[skarlot]

n.o. Octopus, Synergy /w broadcast and Multibox do that. This is not a broadcasting app, I'm gettin tired of saying it.

[Frosty]

So Skarlot, how can I click in my main window and have my other WoW's get the click???? :P

Just kidding! This is still working great for me (not just for WoW). Keep up the good work!

[Prepared]

I have stated this is going to stay a non broadcasting application... the reason being it will lead to another Octopus. Like, if it does multi client mouse looking, then it might need a click list, then a key list and so on. That's not what I have in mind.

This was written seperately because I wanted to build up a KM that was going to work, and not be buried inside any project - especially Octopus, because I have in mind to rewrite so much of that anyway. Then I have options such as, integrating it into a new octopus, or simply having it as my sole KM. That all depends on how things go. From a development point of view, its nice to have a stable KM so I can build a broadcasting app (that will definitely crash from time to time) and then I can easily access the other PC's.. something I cant do developing Octopus. Thats a drawback to all in one. So in short, I don't know what I'm going to do but I'll be developing a different application that either works with or contains this KM.

Been looking at this for awhile. Not yet tried it but am wondering why it won't work with Octopus if the Mouse Hook in Octopus is disabled. I really like the capabilities in Octopus especially the ability to use ALT/SHIFT/CTRL keys to multiple clients across multiple machines. I don't really use the mouse hook in Octopus anyway. Would this work with Octopus if the Mouse Hook was disabled? Was going to give it a try but if anyone knows it won't work it will save me some time.

[skarlot]

Octopus will always think the server is focused so it will avoid injecting keys to the foreground window if this app was on a client.
Then it would also, if allowed to see key hook events (there is an option for that in this), double key in the foreground window where this app has the mouse on clients at the very least.

Something like that.