Build 13 - Bug Report

Quote:

---

This happens because Mojo tells the OS that it needs administrative privileges every time it runs because if it doesn't have them, it can't send keystrokes to programs that are running as admin and it will appear to be broken.

---

This makes perfect sense, and is actually a good thing. I'll just have to figure out how to modify a shortcut in Win7 to have it auto-launch as admin. I'm a Win7 newbie. :)

[quote\1. I think you're talking about broadcasting to computers rather than broadcasting to windows. Is that right? Those two things are actually quite different from each other. Broadcasting to a computer is what mouseover does when you're moused over, except it only does it with one computer. I could very easily make a fourth mode of the program (in addition to mouseover, broadcast, and hotkeys) where it broadcasts to all computers simlultaneously. Is this what you mean?
[/quote]

Right. Keep in mind i'm a long time hardware broadcaster. With my Vetras - there is no "on" or "off" states. If I'm using the broadcasted keyboard - its broadcast to all PCs. To not broadcast to a particular PC - I had to physically unplug the input cable (Ps/2 in my case).

But this brings up an interesting option. The main window to Mojo - it shows you all the conntected computers. Perhaps you could "click" on the ones that you want enabled for broadcasting? (or mouseoever?). Just an idea.

Quote:

---

2. As far as broadcast-to-windows goes, I'm planning to implement it one game at a time. First I'm going to make it work as perfectly as possible with WoW.

---

Understood. This makes sense - but maybe you could have it show what window its "hooked" too (obviously WoW, but maybe just some kind of GUI indicator that it detected WoW and is going to broadcast to it?).

Quote:

---

3. As far as launching goes, I'm planning to handle that through the GUI, not through broadcast. The "WoW" and "Team" and "Toon" screens will be used for that. This may be in the next build. In other words, you'll be able to right click a toon or a team and select "launch" and that toon or team will get launched. But maybe this is too automatic and you'd rather do it manually with broadcast.

---

This is what both Keyclone and Innerspace/ISBoxer are doing. Seems to be the norm - so I'd go with it. Would make things *really* simple for cross PC communication.

What I've always done is just put the WoW launch icon at the top of my Windows Start menu. When I wanted to launch all clients:

"start button" or "control esc"
"down arrow"
"enter"

....and that would fire up WoW on every computer. This is just my personal habits. Everyone does it differently. Being that I started with just straight broadcasting, my approach to multiboxing is often quite different from other peoples. I tweak the program (game) to work around the broadcasting - it seems 99% of the newer folks tweak the broadcaster (software) to the game. I'm backwards. :D

Quote:

---

Okay, that's what I guessed. Two KM programs running at the same time are like two male alpha gorillas in the same house

---

So, after another round of reboots, everything seems to be playing nicely. Input Director starts with Windows. I use it for the "mouseover" KVM functionality only - going from PC to PC.

I launched MOJO after that, and it seemed to play just fine. I turned off the "mouseover" button, and only turned on the "broadcasting" button - everything went fine. There was on pull in H UK where CTRL and ALT seemed to get "stuck" - I had to hit them a few times each to get them to clear. I wasn't able to reproduce the error, so I can't tell you what caused it.

Quote:

---

Right, that's temporary. The program is going to do three different things (broadcast, mouseover, and hotkeys). These things conflict with each other to some extent so I'll probably get all three working before I try to make them cooperate. Maybe I should change the green buttons so only one is on at a time.

---

That would make things less confusing on the surface for sure. :) Also I don't see a way to tell which copy of MOJO is "master". Again, I'm running it on multiple PCs where most people aren't - so i'm the odd man out.

Quote:

---

Originally Posted by Fursphere

This makes perfect sense, and is actually a good thing. I'll just have to figure out how to modify a shortcut in Win7 to have it auto-launch as admin. I'm a Win7 newbie. :)

---

On Vista, you have to disable UAC to do that and I'd expect it's the same on Win 7. Maybe there's a way to disable it just for that one program but if so you'll probably have to disable it again when Mojo updates to the next build. Personally I love UAC and knowing what it's doing, I don't mind the prompts.

Quote:

---

Right. Keep in mind i'm a long time hardware broadcaster. With my Vetras - there is no "on" or "off" states. If I'm using the broadcasted keyboard - its broadcast to all PCs. To not broadcast to a particular PC - I had to physically unplug the input cable (Ps/2 in my case).

---

That's a good way to think about it. This is like hardware broadcasting. This didn't occur to me since I've never used any hardware KVM stuff or swtiches or anything of that sort.

What do you think about a fourth button at the top of Mojo's window for "hardware broadcasting"? Maybe that's too confusing. I've been hoping that somehow hardware broadcasting can be merged invisibly into some other part of the interface.

Quote:

---

But this brings up an interesting option. The main window to Mojo - it shows you all the conntected computers. Perhaps you could "click" on the ones that you want enabled for broadcasting? (or mouseoever?). Just an idea.

---

Good idea. Let's talk about this in more detail as that screen develops. Those PCs will have a right click menu (all icons will have right click menus). The PCs can change appearance to indicate various things such as whether they are receiving broadcasts. There can also be what Microsoft calls a tooltip which means text appears when the mouse cursor hovers over the picture.

(continued below)

Quote:

---

Originally Posted by Fursphere

Understood. This makes sense - but maybe you could have it show what window its "hooked" too (obviously WoW, but maybe just some kind of GUI indicator that it detected WoW and is going to broadcast to it?).

---

The "WoW" screen will have an icon for each Wow on the network, and the icons will show somehow which ones are running, which ones are receiving broadcasts, etc. Is that what you mean?

Quote:

---

What I've always done is just put the WoW launch icon at the top of my Windows Start menu. When I wanted to launch all clients:

"start button" or "control esc"
"down arrow"
"enter"

....and that would fire up WoW on every computer. This is just my personal habits. Everyone does it differently. Being that I started with just straight broadcasting, my approach to multiboxing is often quite different from other peoples. I tweak the program (game) to work around the broadcasting - it seems 99% of the newer folks tweak the broadcaster (software) to the game. I'm backwards. :D

---

I think you're exactly right. I'd like Mojo to be flexible so people can use it however they like. You've convinced me to make it emulate hardware broadcasting.

Quote:

---

I launched MOJO after that, and it seemed to play just fine....

---

The order in which you launch Input Director and Mojo may make a difference because probably both programs are installing low level hooks, and depending on which one installs first, one of them can hide keyboard and mouse events from the second. (This can happen inadvertently.) I think the one that installs second can hide events from the first but maybe it's the other way around. I try to write Mojo so it never hides anything.

Quote:

---

Also I don't see a way to tell which copy of MOJO is "master". Again, I'm running it on multiple PCs where most people aren't - so i'm the odd man out.

---

There isn't any master. All copies of Mojo have the same abilties. No masters, no slaves, no servers, no clients. Just Mojos. :)

Edit: However the settings on one Mojo don't necessarily affect another Mojo. This may change as the program develops. Right now, for example, if you set mouseover layout on one PC, it doesn't affect the mouse that's plugged into another PC. You need to set the second PC's mouseover layout separately if you want to mouse over with that PC's mouse.

Quote:

---

There isn't any master. All copies of Mojo have the same abilties. No masters, no slaves, no servers, no clients. Just Mojos.
Edit: However the settings on one Mojo don't necessarily affect another Mojo. This may change as the program develops. Right now, for example, if you set mouseover layout on one PC, it doesn't affect the mouse that's plugged into another PC. You need to set the second PC's mouseover layout separately if you want to mouse over with that PC's mouse.

---

I actually figured this out last night. The Input Director + Mojo setup an yeild some quite interesting results

When I mouseover to another screen with ID - that becomes the lead computer for "input" Mojo sees this, and depending on each PC's Mojo settings, different things happened. (broadcast on or off).

So the "main" was where ever my mouse was, and the broadcasting was done on a PC mojo window basis. Took me a minute to figure out what was going on. :)

Also, whats up with the install path for Mojo? I'm used to things going in Program Files - not Users\Appdata\roaming profiles? Seems a bit odd to me.

Quote:

---

Originally Posted by Fursphere

Also, whats up with the install path for Mojo? I'm used to things going in Program Files - not Users\Appdata\roaming profiles? Seems a bit odd to me.

---

It uses Microsoft's ClickOnce deployer. The location is normal for ClickOnce. ClickOnce always caches binaries in %appdata%.

You can copy Mojo's files and put them somewhere else if you want.

http://msdn.microsoft.com/en-us/libr...d(VS.100).aspx

Ahh Microsoft... all makes sense now. lol

People often think ClickOnce is weird. I did too when I first saw it. But if you look at what it does (updates Mojo automatically) instead of how it does it (caches Mojo in hidden directory) I think it's a pretty good fit for Mojo.

The only real objection I've heard is that some people's %appdata% is on a small SSD and they don't want to put stuff on that SSD. But Windows lets people move %appdata% to another hard disk if they want, so that's not a problem.

Earlier versions of ClickOnce had a problem with vanishing desktop shortcuts but that seems to be fixed in the new beta version that Mojo's using.

If there are problems with ClickOnce or it turns out to be buggy (previous versions were buggy) I'll replace it with a traditional installer. I'm just trying it out and seeing people's reactions.

FYI - I just pulled my Vetra multiplexers out of my rack. (and about a dozen cables...)

I'm feeling a little strange right about now.

Holy crap. :)

What made you decide to do it?

Damn Razer Naga mouse was the catalyst. No way to hardware broadcast this thing....

I'm exclusively using Mojo to broadcast too. Its a litle cumbersome having to click "on" and "off" - but I'm dealing with it. lol