Build 13 - Bug Report

[Fursphere]

I don't see a mojo bug report thread, so I'll start one.

Build 13 - Broadcasting only.

I just received a Razer Naga mouse as a gift, so I figured I'd use Mojo to get things rolling. The software flat-out REFUSES to pass the NUMPAD 2 button. Either on the mouse or on the keyboard, it won't pass.

I have verified both buttons (keyboard and mouse) to be working outside the software, so no problems there.

Also, the lack of a broadcast on / off toggle key is killing me! How am I supposed to chat? lol

thanks

-Fur

[Fursphere]

Also, not really a bug - but Mojo does interfere with Input Director KVM operations. Running both at the same time gets some strange results (things like mouseover to next PC just randomly start/stop working)

[Freddie]

I don't see a mojo bug report thread, so I'll start one.

Build 13 - Broadcasting only.

I just received a Razer Naga mouse as a gift, so I figured I'd use Mojo to get things rolling. The software flat-out REFUSES to pass the NUMPAD 2 button. Either on the mouse or on the keyboard, it won't pass.

Thanks for the report. Is NumLock on? If this still happens with NumLock on, could you please copy and paste the info that appears in "Your last action" when you press Numpad2 on the keyboard. Thanks.

Edit: I just tested this and it works okay on my computers with both PS2 and USB keyboards.

When NumLock is on, Numpad2 sends a 2 character. With NumLock off, the same key sends a down-arrow character.

To the operating system (and to Mojo) those are two different keys even though the same piece of plastic is used.

[Also, the lack of a broadcast on / off toggle key is killing me! How am I supposed to chat? lol

Click the green Broadcast button on the main screen. There will be other ways to do this in future bulids, but for now, that's the only way.

[Freddie]

Also, not really a bug - but Mojo does interfere with Input Director KVM operations. Running both at the same time gets some strange results (things like mouseover to next PC just randomly start/stop working)

Mojo shouldn't have any effect on other KM programs unless the mouse cursor leaves the local display.

If Mojo is affecting Input Director without the mouse cursor going past the edge of the display, it's a bug or design flaw in one or both programs.

I don't think Mojo has either but I'll look at the source code again and try to make sure.

[Fursphere]

The numlock thing - every other numlock button works fine. Its just NUMLOCK 2. Thats what tipped me off - I use 1 - 5 for healing. 1,3,4,5 were working, but 2 just wouldn't go. I made sure it wasn't the new mouse by using the keyboard - same result.

When I used software boardcasting in the past, I just F12 to toggle on / off the boardcasting fuctionality. That's what I was referring to above - having to alt-tab and click a box isn't realistic.

The "mouse over" part of MOJO basically replicated what Input Director does now. (although if the mojo window is "active" it won't pass over to the next PC, I have to click on the desktop then it'll pass...). Mojo is *almost* perfect in its basicaly functionality - for me.

I'm old school. No key maps. No do not pass lists. I just want "on and off" broadcasting. lol

[Freddie]

The numlock thing - every other numlock button works fine. Its just NUMLOCK 2. Thats what tipped me off - I use 1 - 5 for healing. 1,3,4,5 were working, but 2 just wouldn't go. I made sure it wasn't the new mouse by using the keyboard - same result.

Could you click "Geeky stuff" on Mojo, try to broadcast Numpad2, and copy the messages that Mojo displays so I can see them?

When I used software boardcasting in the past, I just F12 to toggle on / off the boardcasting fuctionality. That's what I was referring to above - having to alt-tab and click a box isn't realistic.

I understand. You'll be able to toggle it with a hotkey. Like I said, it will be in future builds.

The "mouse over" part of MOJO basically replicated what Input Director does now. (although if the mojo window is "active" it won't pass over to the next PC, I have to click on the desktop then it'll pass...). Mojo is *almost* perfect in its basicaly functionality - for me.

Well let's try to get it perfect!

Does this problem with Mojo active/inactive happen when Input Director is not running?

[Fursphere]

Ok - the mouseover thing seemed to be a conflict between Mojo and input director. I did a full reboot and shut down input director before starting mojo, and the problem is gone. It no longer cares if its foreground or background - mouse passes over to next PC either way.

Numlock thing: How do I test this WITHOUT WoW running? I'm used to software broadcasting being "on or off" - not program specific. It seems the broadcasting on works "inside" of WoW ?

EDIT: used the login screen to test.

Ok, it seems to be working fine now (weird!). Its either an incompatiblity with Input Director, or something wonky when I first launched Mojo? Anyway, it works now.

Couple of notes, as I think you may already be aware of:

1) Mouseover enabled kills broadcasting. Can't use both at the same time right now.
2) All of the buttons "WoWs" "Toons" "Teams" don't seem to do anything with a multiple PC setup. I've seen screenshots of them doing stuff - so I'm assuming its just my setup.
3) A feature that would turn numlock on on all PCs when WoW launched would be awesome. I currently use a little utility and a batch file to do this - so they're all synced when I fire up WoW.

[Fursphere]

I'm using Windows 7 Pro on all clients btw. Launching Mojo causes the Windows UAC to throw a fit.

I have to "authortize" it every time I launch it.

The selective broadcasting is a mixed blessing for me too. I like that its not always on - and only auto-enables itself when it detects WoW running - but I've also gotten used to have it broadcast in Windows, so I use it quite often (mass launch programs and also how I launch WoW x5)

[Freddie]

Ok - the mouseover thing seemed to be a conflict between Mojo and input director. I did a full reboot and shut down input director before starting mojo, and the problem is gone. It no longer cares if its foreground or background - mouse passes over to next PC either way.

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

Numlock thing: How do I test this WITHOUT WoW running? I'm used to software broadcasting being "on or off" - not program specific. It seems the broadcasting on works "inside" of WoW ?

EDIT: used the login screen to test.

That's how I test too (with WoW's log in screen). This build of Mojo only broadcasts to WoW. You can't test it with any other program. My plan is to make Mojo work perfectly with WoW, then later add more games.

1) Mouseover enabled kills broadcasting. Can't use both at the same time right now.

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.

2) All of the buttons "WoWs" "Toons" "Teams" don't seem to do anything with a multiple PC setup. I've seen screenshots of them doing stuff - so I'm assuming its just my setup.

Toons was enabled in an earlier build but it didn't really do anything so I turned it off in build 13. Right now I'm writing the real code for those buttons, and they will all gradually begin to work for real in the next few builds.

3) A feature that would turn numlock on on all PCs when WoW launched would be awesome. I currently use a little utility and a batch file to do this - so they're all synced when I fire up WoW.

Okay, I'll add that when I do the "launch WoW" stuff. That may be in the next build, I'm not sure yet.

[Freddie]

I'm using Windows 7 Pro on all clients btw. Launching Mojo causes the Windows UAC to throw a fit.

I have to "authortize" it every time I launch it.

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.

HotkeyNet doesn't do this, and as a result, people constantly think HotkeyNet is broken when actually they just need to run it as admin. I decided to avoid this problem with Mojo by making it require admin privileges on its own.

If you have a better idea about how to handle this, please tell me.

The selective broadcasting is a mixed blessing for me too. I like that its not always on - and only auto-enables itself when it detects WoW running - but I've also gotten used to have it broadcast in Windows, so I use it quite often (mass launch programs and also how I launch WoW x5)

This opens up a couple of different issues so please bear with me.

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?

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.

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.

What do you think?