Build 16: Alt-tab bug fixed

[Fursphere]

Question about how "mouseover" works.

When you use Mojo to mouse over to another mojo (basically software KVM), does the new PC become the "focus" point from where things are broadcast?

PC 1 mouses to PC 2. Assuming broadcast is turned on on both mojos

Are keys now boardcast from the focal point of PC 2? or Still from PC 1?

[Moorea]

I saw later the build15 post :-)

About DNP... while a different DNP for different Wow is maybe nice; the basic DNP I need is just same DNP for every window (but the one that has the mouse, which obviously gets all the keys)

ps: not sure if that's in but a cool feature would be to automatically pause broadcasting if I mouse out of a wow window (maybe with a small time delay so it doesn't stop if I mouse travel from 1 wow to another while going over other windows) - the idea there is that if I switch to my web browser to check wow head; I wouldn't have to pause bcasting manually to type a search

[Fursphere]

This is what Freddie and I have been dicussing offline for the "keymap / DNP" interface. This is just a basic mockup, but it'll give you an idea.



As Freddie has stated, there are a few items that need to come first.

[Freddie]

Question about how "mouseover" works.

When you use Mojo to mouse over to another mojo (basically software KVM), does the new PC become the "focus" point from where things are broadcast?

PC 1 mouses to PC 2. Assuming broadcast is turned on on both mojos

Are keys now boardcast from the focal point of PC 2? or Still from PC 1?

From PC2. At least that was my intention. I didn't test it too carefully.

How do people think it should work?

[Ghallo]

This is what Freddie and I have been dicussing offline for the "keymap / DNP" interface. This is just a basic mockup, but it'll give you an idea.



As Freddie has stated, there are a few items that need to come first.

Does WoW Client 1/2/3/4/5 change based on Focus?

[Fursphere]

Does WoW Client 1/2/3/4/5 change based on Focus?

No - but sorta.

This is a keymap from MOJO #1's point of view (PC1 in my case).

PC2 would have a slightly differnet keymap. Same for 3,4,5.

But you bring up a good question about same-box multiboxing. Hmm....

EIDT: I'm thinking make it based on which window has "FOCUS" (windows focus, not WoW focus) at the time. But thats a question for Freddie.

[UNIXman]

From PC2. At least that was my intention. I didn't test it too carefully.

How do people think it should work?

I love it that the machine with the focus gets the keyboard. If it can be made an option, even better!

[Owltoid]

Sorry if this has been covered (I try to keep up to date on the Mojo news), but will Mojo be as efficient in mouse broadcasting as ISBoxer? I love the flexibility of HKN, and given the scripting nature I doubt ISBoxer can do all that I'm doing through HKN, but the consensus is ISBoxer is the clear winner for mouse broadcasting. I'm not sure why it works as well as it does, so all I can ask is an uneducated question of if Mojo will work as well.

[Freddie]

EIDT: I'm thinking make it based on which window has "FOCUS" (windows focus, not WoW focus) at the time. But thats a question for Freddie.

edit: on second thought let me rewrite my answer

edit: this is complicated, I'm drawing pictures.

[Freddie]

Sorry if this has been covered (I try to keep up to date on the Mojo news), but will Mojo be as efficient in mouse broadcasting as ISBoxer? I love the flexibility of HKN, and given the scripting nature I doubt ISBoxer can do all that I'm doing through HKN, but the consensus is ISBoxer is the clear winner for mouse broadcasting. I'm not sure why it works as well as it does, so all I can ask is an uneducated question of if Mojo will work as well.

I don't know how ISBoxer is written (I've never seen it let alone looked at it in a debugger) but I suspect it hooks DLLs and injects code. Mojo won't do those things.

Given that difference, I don't know if I can make Mojo inject mouse events as quickly as Lax's software. All I can say is that I'm going to try. Wish me luck.

I'm planning to use different code in Mojo for injecting mouse events than the code in HotkeyNet.

Also, I may add a device driver to Mojo at some point which would let me do some low-level chicanery, and that might help too.

Something to think about is, Mojo will probably get "finished" in 2012. Then figure it's widely used for five years before it becomes obsolete compared to its competition.

During Mojo's lifetime, 16 and 32 core CPUs will be normal. On that kind of hardware, I think any method of injecting mouse events, even crappy methods, will be fast enough to appear instantaneous.