Unofficial Mojo FAQ

[Freddie]

Toggle hotkeys.

4 - Not sure what you mean here

Just like there's a toggle for mouseover mode and a toggle for broadcast mode, there will be a toggle for hotkey mode.

The toggle wil determine whether user-defined hotkeys get triggered when their key combos are pressed.

Hotkey mode is different from the hotkeys we're discussing here. The hotkeys in this thread have pre-defined actions that I'm building into the program. Hotkey mode is for hotkeys with actions that have been designed by the user.

[Fursphere]

I see. This must be where HotKeyNet gets integrated into Mojo?

[Freddie]

I see. This must be where HotKeyNet gets integrated into Mojo?

Yeah.

To be more exact, this is where the kinds of features that HotkeyNet has will be integrated. I'm not going to reuse HotkeyNet's code. The features will be redesigned and rewritten.

[Moorea]

Hey, I (and many more) would use Mojo if it had a few very basic features (already mentioned a few weeks back but I'll reiterate my wish list, in order of priority) :


- Do not pass list (WSAD...) mode but also keep "Broadcast all" mode + add missing pause mode - 3 modes key toggled with visual indication (movable semi transparent overlay would be nice)
- (Movement keys) [this actually is probably in already]
- Wow window resize move and unframe
- mouse broadcasting mode (ideally without actually moving the real mouse cursor in each window, yet sending all events - if wow was a drawing app it should be possible to draw on 1 and have same drawing on additional windows)

Nice to have

- cursor on all windows for preview of mouse broadcasting effect

[Freddie]

Hey, I (and many more) would use Mojo if it had a few very basic features) ...

I think so too. Pretty soon we'll cross a threshhold and suddenly the program will have a ton of users. I'm dreading it and looking forward to it at the same time.

I'm thinking we're in the calm before the storm -- enjoy it while it lasts.

- Do not pass list (WSAD...) mode ...

In order to do this I needed two other features to build on. (1) A system of storing config info and (2) a way for the program to keep track of individual WoWs. I wrote (1) in December during the long pause between builds and I'm writing (2) now. So pretty soon the program will have no-pass lists.

(I keep saying "keep track of WoWs" but what I really mean is launch WoWs and retain a way of targeting those known launched WoWs.)

I know you keep wanting me to put simple things in the program right away. I don't mind doing that if the simple code takes just a few minutes or if the simple code can grow, but in this case, if I write a quick-and-dirty no-pass system, it'll take a few days and then I'll have to throw the simple code away and replace it with new code, I'd rather just write the real code in the first place.

add missing pause mode - 3 modes key toggled with visual indication (movable semi transparent overlay would be nice)

I'm writing the hotkey-toggle stuff right now as a result of Fursphere's comments. By the way the program is going to have four modes, not three because Fursphere made me realize that broadcast-to-windows and broadcast-to-computers are separate important modes.

The overlay could be added easily but I don't know if that's the best use of my time at this early stage when so many core features need to be created.

- (Movement keys) [this actually is probably in already]

Broadcast mode can do movement keys. The underlying key-injection code is finished and it handles movement keys fine.

- Wow window resize move and unframe

This had to wait until the program can keep track of individual WoWs.
Also I want to make a really really nice graphical interface for PIP / maximizer / layout / whatever you call all that stuff generically.

- mouse broadcasting mode (ideally without actually moving the real mouse cursor in each window, yet sending all events - if wow was a drawing app it should be possible to draw on 1 and have same drawing on additional windows)

Broadcast of clicks will be extremely easy to add -- I'll do that very soon.

Broadcast of drags (i.e. the ability to draw, that's a good way to describe it) -- I'm going to try to do this, it may turn out to be easy. I've never tried before so I don't know. Does anybody know if Octopus can do it without its optional hook code and without its optional filter driver? If Octopus can do it with those limitations, then it will be easy for me to add it to Mojo.

- cursor on all windows for preview of mouse broadcasting effect

I'm working under the restrictions with Mojo of using only the normal OS API. Therefore no hooking of DLLs. I don't know if this is possible under these limitations.

If somebody wants to help with this they could read the MSDN documentation for new stuff in DirectX 10 and 11 and the new desktop window manager API stuff in Vista, etc., and see if they can find a way.

[Fursphere]

I'm writing the hotkey-toggle stuff right now as a result of Fursphere's comments. By the way the program is going to have four modes, not three because Fursphere made me realize that broadcast-to-windows and broadcast-to-computers are separate important modes.

The overlay could be added easily but I don't know if that's the best use of my time at this early stage when so many core features need to be created.

I <3 Freddie.

Agreed that the overlay would be extremely nice - but can sit on the back burner for awhile.

On the broadcast subject, I think we talked about this - but once Mojo understands that each wow is a serperate wow, it would be nice to turn off each wow individually. (multi-PC multi-client setups... like 2 on one, 3 on another).

[Freddie]

I <3 Freddie.

Aw shucks

On the broadcast subject, I think we talked about this - but once Mojo understands that each wow is a serperate wow, it would be nice to turn off each wow individually. (multi-PC multi-client setups... like 2 on one, 3 on another).

Yeah definitely.

[Moorea]

Agree that some overlay to display infos/modes can wait, it's "nice to have"

I'm working under the restrictions with Mojo of using only the normal OS API. Therefore no hooking of DLLs. I don't know if this is possible under these limitations.

I wasn't thinking of showing the real cursor but maybe just your own drawing on top of the screen at the location the click, etc... would go (in a way that relates then to the previous item)

Again, take your time, I'm happy with HKN in the meantime (and my daughter can wait to box until next break)

[Freddie]

I wasn't thinking of showing the real cursor but maybe just your own drawing on top of the screen at the location the click, etc... would go (in a way that relates then to the previous item)

Are you saying that Mojo should do its own drawing? Yes, absolutely, it would have to. But it has to use operating system services to do the drawing. The drawing has to be very, very fast and it can't mess up the graphics in the window beneath it. These are difficult requirements because the underlying window is using DirectX to composite its graphics on the video card and (so far as I know) the operating system doesn't provide any way for some other process (i.e. Mojo) to mix its own graphics into the first process's DirectX composition. But there are lots of nooks and crannies in the ecosystem created by the video driver, DirectX, Windows desktop window manager, etc., and Microsoft has added a lot of new stuff in these areas over the last couple of years, so maybe there's a way.

Or are you saying the drawing doesn't have to look like a cursor but could look like something else?

[Moorea]

in windowed mode, I can have for instance a 20% opaque/transparent clock widget on top of my wow windows (always on top; opacity 20%) - so rather than manipulate the OS cursor, can you plug in that way maybe ? and yes I meant the shape drawn doesn't have to be what the actual custom cursor from the game would be and maybe just a simple cross hair instead - if that makes the problem simpler

ps: that opacity setting, assuming its an OS support, could be a good way to easily overlay the status window maybe ? the alternative is however the volume controls show up sometime (green bars on top of the screen)