Unofficial Mojo FAQ

[Fursphere]

What is the scope / timeline for do-not-pass / keymaps in Mojo Freddie?

[Freddie]

Right now I'm finishing the code that allows the program to keep track of which WoW is which.

As for timeilne, I haven't decided what to do next. You seem to be the only person who's actually using the program, so you tell me. What do you want next?

As for scope, I figure I'll keep adding features that people ask for.

I'm planning to let the design evolve through a back-and-forth process with users so I don't have a fixed idea about how it will turn out.

[Fursphere]

Well, if i'm the only one, I guess I should start testing same-box multiboxing as well, at least in a limited scope. (I'll get on that this weekend - hehe)

For me personally, my wishlist would be in this priority

1) Hotkey for toggling broadcasting on and off. Mousing over to the button is easy enough since I've got mojo on my second monitor, but if it was in the background, it would be a PITA.
2) Keymaps - at least in a basic form. Like a "do not pass" list or something - I'm playing toons solo more and more these days, and having to constantly bind and unbind movement keys it driving me nuts.
3) Mojo disconnect option. Sure, I can CLOSE mojo right now to kill broadcasting to that PC, but it would be nice if I could do it from within mojo so "stop accepting inputs from another mojo" type of this.

I'm use Input Director for my software KVM solution - so the "mouse over" features of mojo are very low on my personal priority list - in fact, they are no needed at all for "single PC" multiboxers.

[Freddie]

Well, if i'm the only one, I guess I should start testing same-box multiboxing as well, at least in a limited scope. (I'll get on that this weekend - hehe)

Thanks but I don't think you have to go out of your way to test stuff you're not using. As the program gets more complete, more people will use it and stuff will get tested.

For me personally, my wishlist would be in this priority

1) Hotkey for toggling broadcasting on and off....

Okay, I'll do that next after the WoW stuff that I'm finishing now. But I won't just add that single hotkey. I'll add a page of hotkeys that affect Mojo. Not sure what to call them. Built-in hotkeys? Hm, no, that makes it sound like you can't choose the key combos that trigger them.

I guess I'll include hotkeys for:

Toggle broadcast.
Toggle mouseover.
Bring cursor home from mouseover.
Toggle hotkeys.
Minimize Mojo to taskbar/restore to normal

What else?

[Freddie]

duplicate post.

[Akoko]

I'm just curious, how complicated is it to have a mouse cursor in each window? Of course I wouldn't be expecting a feature like this anytime soon.

Anyway, keep up the good work! I eagerly look forward to the next release of Mojo. I'll likely be using it as my main program once I can add scripts to it, instead of my current clumsy combo of multiple programs...

[Freddie]

I'm just curious, how complicated is it to have a mouse cursor in each window? Of course I wouldn't be expecting a feature like this anytime soon.

It's easy to make the program click in multiple windows simultaneously and Mojo will do that soon.

I'm planning to implement that without making the cursor visible in multiple windows. I don't know if there's an easy way to make it visible.

[Akoko]

It's easy to make the program click in multiple windows simultaneously and Mojo will do that soon.

I'm planning to implement that without making the cursor visible in multiple windows. I don't know if there's an easy way to make it visible.

Yeah, I guess not. The main problem I've been having with HKN broadcasting is if I accidentally hold down the mouse button or move very slightly it can severely mess up the views or change focus of one or all of my WoW windows, and sometimes the clicks don't pass reliably. Maybe it's just my script that isn't optimal, rather than HKN's system itself?

This is what I'm using:

<Hotkey Alt LButton, MButton, RButton, Button4, Button5>
   <SendLabel w1, w2, w3> 
      <ClickMouse %TriggerMainKey%>

If the problem extends further than just my script, then I patiently await Mojo's mouse broadcasting

P.S. Would it be possible to have a feature that compensates for the existence of pet bars or totem bars somewhere down the line? I've noticed that all of my shaman's dialogue buttons such as Need/greed loot windows are higher up than those on my mages simply because of the totem castbar, meaning I have to click once for the shaman and then once for the mages.

[Fursphere]

I guess I'll include hotkeys for:

1) Toggle broadcast.
2) Toggle mouseover.
3) Bring cursor home from mouseover.
4) Toggle hotkeys.
5) Minimize Mojo to taskbar/restore to normal

What else?

1 - Yes plz.
2 - Yes plz.
3 - Input director does this and I RARELY use it. Could be handy though?
4 - Not sure what you mean here
5 - Don't think this is needed honestly.

[Freddie]

Yeah, I guess not. The main problem I've been having with HKN broadcasting is if I accidentally hold down the mouse button or move very slightly it can severely mess up the views or change focus of one or all of my WoW windows, and sometimes the clicks don't pass reliably. Maybe it's just my script that isn't optimal, rather than HKN's system itself?

This is what I'm using:

<Hotkey Alt LButton, MButton, RButton, Button4, Button5>
   <SendLabel w1, w2, w3> 
      <ClickMouse %TriggerMainKey%>

The script is fine but it sounds like your settings and/or send modes are sub-optimal. Since I don't know your send modes and settings, I'm only guessing.

One of the problems with HotkeyNet is that it has so many options and alternative code paths that it's impossible to help a user without first asking him twenty questions.

Mojo is going to use a different method for injecting keystrokes and mouseclicks than the ones in HotkeyNet. The new code is already used in Mojo for key broadcasting. The new method is simpler, faster, and more reliable. It has no user-settable options so I will never have to ask anyone, "What are your settings?"

P.S. Would it be possible to have a feature that compensates for the existence of pet bars or totem bars somewhere down the line? I've noticed that all of my shaman's dialogue buttons such as Need/greed loot windows are higher up than those on my mages simply because of the totem castbar, meaning I have to click once for the shaman and then once for the mages.

I don't know very much about WoW so I'm going entirely by your description here, but it sounds like yes, this could be done. It could be done now with HotkeyNet too.