Build 14: New code for injecting keystrokes

[Freddie]

what I envisioned for this tab would do is a place to configure know mojo paths, similar to how the wow tab works to know where the know wows are.

Each Mojo already knows about the others. They find each other automatically. The Computers tab shows other Mojos. It's called "Computers" instead of "Mojos" because I thought the name "Mojos" would be confusing in this context.

Mojos don't remember anything about each other. Each Mojo only knows about another while the other is running and they are connected. It's done this way because it guarantees that every Mojo's info about the others is correct. By designing it this way, a whole class of errors is prevented.

This would not be a master/slave becouse these settings could be done from any Mojo and pushed to any other...

I agree.

By the way, in order to copy info from a local PC to a remote PC, the local Mojo needs the IP address and/or hostname of the remote Mojo, not the pathname. The local Mojo needs to ask the remote Mojo to save the settings, and it does this by sending info over a socket connection, not by doing anything with the remote PC's hard disk.

There are two reasons why a Mojo doesn't mess with the hard disk on a another computer.

1. The OS on the PC where the hard disk is located may not allow another PC's Mojo to read or write the file. (Mojo runs with admin privileges but they only apply to the PC where that instance of Mojo is running.)

2. If more than one Mojo could write to the same file, the file could become corrupted or out of sync with other data.

[Fursphere]

BUG REPORT!

So, I'm not sure how to reproduce this one, as it is a bit strange.

I'm currently playing with 4x feral druids. Just hit level 30 (yay me!). Anyway, so I learned feral charge and assigned it to the "1" key. Acquire target - hit "1" - only main flys in. Hmmmm....

Try doing one of the followers solo - get target, hit 1, nothing happens - WoW gives "target too close" error (even thought I know its not). I try this sort of thing 20 different ways in five minutes. I'm totally able to pass the "1" key in chat windows. I hit 1 and I see the wow action bar light up - but the actual ability doesn't get used.

So, I close mojo and try it (moused over to the alt) - and it works! Rinse repeat on all 3 "alt" PCs, and it fixes the problem. Strange right? Other keys were working fine....

So I reload mojo on every PC, and so far so good, everything appears to be working fine - including the "1" key.

I had similar problems lately with left mouse clicks on alts - I usually have to reload WoW to fix the issue. I honeslty don't know if its Input Director or Mojo - but reloading Mojo did fix it. If it happens again, I'll try closing input director first to see what happens.

So ya, don't have much to go on, but _something_ is acting goofy.

[Freddie]

BUG REPORT!

Fun fun fun!

get target, hit 1, nothing happens - WoW gives "target too close" error (even thought I know its not).

Is WoW displaying "target too close" in response to your keystroke? If so, then it's doing something.

Key broadcast can only break in two ways:

(1) WoW doesn't receive anything, or

(2) WoW receives the wrong key info.

If you press a key and WoW doesn't react at all, it's problem (1). If WoW displays an error message (or does anything else) it's problem (2). From my point of view, that's a big difference.

If it's (2), can you figure out what key info WoW is receiving based on what it does?

I try this sort of thing 20 different ways in five minutes. I'm totally able to pass the "1" key in chat windows. I hit 1 and I see the wow action bar light up - but the actual ability doesn't get used.

What key strokes would WoW have to receive to make WoW's action bar light up?

Would that happen if Shift or Alt or Ctrl is down?

If it happens again, I'll try closing input director first to see what happens.

Thanks, sounds like a good idea.

Also, next time it happens, could you broadcast Alt Ctrl Shift to all your WoWs (press and release those three keys in no special order) and see if that fixes the problem.

[Fursphere]

Ok, got it to do it again. Shutting down Input DIrector (on all machines) solved the problem.

Its going to be near impossible to tell if its a bug in IP - a bug in Mojo - or an incompatibility with the two running at the same time. (I'm running a beta version of Input Director to boot. lol).

So.. whats the status of getting mouseover in Mojo working at the same time key boardcasting is on?

[Fursphere]

Ok - 3rd times the charm. Figured it out. Its the CTRL-ALT sticky thing again.

ALT-1 stills shows the action bar being "hit" but its not actually clicking the button. After "rolling" the ctrl and alt kets a few times, it solved the problem.

This was with Input DIrector shutdown - so its gota be mojo. And I even tried a PS/2 hardware attached keyboard to PC #2 (while it was having the issue) and same results - rolling the ctrl / alt keys "unlocked" them and the "1" key started acting normal again.

[Freddie]

(Edit: This post crossed the one right above it)

We might be able to figure out why the programs are interacting this way. The reason I asked about alt/ctrl/shift is because the only complicated thing Mojo does is keep its own record of whether those keys are down or up.

Today I came within a hair of finishing the new hotkey stuff. Tomorrow, in order to finish it, I have to make some changes to mouseover and to the keyboard hook, and those are the two parts of the program that have to be changed for mouseoever and broadcasting to work at the same time. So I'll try to change it all tomorrow when I'm working on it.

[Freddie]

Ok - 3rd times the charm. Figured it out. Its the CTRL-ALT sticky thing again.

ALT-1 stills shows the action bar being "hit" but its not actually clicking the button. After "rolling" the ctrl and alt kets a few times, it solved the problem.

This was with Input DIrector shutdown - so its gota be mojo. And I even tried a PS/2 hardware attached keyboard to PC #2 (while it was having the issue) and same results - rolling the ctrl / alt keys "unlocked" them and the "1" key started acting normal again.

Good work!

That was my guess ... that's why I asked you to press those keys. Can you figure out a sequence of actions that causes the problem?

If you can do that, I'll probably be able to fix it pretty easily.

[Fursphere]

Honestly, it seems to be tied to when I ALT-TAB in and out of WoW on the main machine - going to the web browser and such. When I go back to WoW, it seems to "forget" where the ALT key is.

Hmm.... just had an Idea. BRB!

EDIT - Strach that . I was thinking maybe it had something to do with how I went back to WoW - either by clicking on the WoW window, bring it back into the foreground, or ALT-TABBING back - made no different.

I have to hit ALT on the slave machine to get it back in sync.

[Freddie]

Honestly, it seems to be tied to when I ALT-TAB in and out of WoW on the main machine - going to the web browser and such. When I go back to WoW, it seems to "forget" where the ALT key is.

Hmm.... just had an Idea. BRB!

EDIT - Strach that . I was thinking maybe it had something to do with how I went back to WoW - either by clicking on the WoW window, bring it back into the foreground, or ALT-TABBING back - made no different.

I have to hit ALT on the slave machine to get it back in sync.

Oh, okay, that explains it. This is the same problem you told me before, right?

Excellent detective work!

I think I know what's wrong but I haven't figured out what to do about it.

I think it's just that when you Alt Tab, by the time you release the Alt key, WoW is no longer the focus window, so Mojo never broadcasts the release of the Alt key.

As a result, Mojo's key state tables (the fake ones it maintains for each WoW) show the Alt key down. Then next time you broadcast a key, Mojo translates the key with the screwed up key state tables. This could have odd effects since the operating system has a complicated way of interpreting keystrokes when Alt is down.

[Fursphere]

Makes perfect sense to me. Hard has is it for mojo to actually verify the keystate?