Mojo build 2 is ready to test ** Testing Closed **

[Freddie]

...then any software which sends repeated key downs would cause this illegal behaviour (or at least this is my concern).

Keyboards generate repeated downs. You're worried about software doing something that every keyboard does constantly.

If you open Notepad and hold down the X key, you'll get a stream of X's because the keyboard automatically repeats X down, X down, X down, X down for a long as you hold the key.

When you see Mojo sending repeated key downs, the source is the keyboard. Mojo is seeing your keyboard generate repeats, so Mojo broadcasts the repeats to the non-focused windows.

The result is simply that the non-focused WoW's see the same thing that they would have seen if they had the focus and you were using only the keyboard.

Perhaps you could interpret this to help me understand it better; is Mojo trying to tell the window I am repeatedly pressing the key (albeit impossible, without releasing it), or is it all quite normal, and I just didn't know that it did it anyway (even with a single window and no Mojo)? Your last line seems to say its not a problem I think? So my keyboard sends these repeated key downs anyway, not just the first key down then wait?

Sorry, I only saw this after I posted the above. Maybe my post crossed with your edit, I don't know.

Yes, your last sentence is correct. Your keyboard sends these repeated downs all the time.

Like I said above, if you open a word processor and hold a key down, you'll see the automatic repeats happen. (I know you've seen this a zillion times, but maybe you didn't connect it with what happens when you play WoW.)

[Freddie]

I think it is that if the key was repeated like if it was multiple keystrokes, it would count/function as getting more than one action per keystroke. Like an autofire function on some game console controllers, where you can hold down a button and it will treat it as multiple rapid presses of the button.

If you could hold down a single key and repeatedly trigger an action from the left side of WoW's key binding screen, that would break the rules.

But you can't do that this way. (Or if you can, you can also do it with an ordinary keyboard.)

[Flekkie]

My name is Flekkie, and I am an editaholic. It started with just one edit in the evenings, but now it's getting out of control.

Ahem.. thanks for the confirmation.

[Freddie]

My name is Flekkie, and I am an editaholic. It started with just one edit in the evenings, but now it's getting out of control.

I'm the same way.

[Fizzler]

Flekkie hit all the things I noticed and than a few.

Under last action key name it shows what was last depressed and not a series of keys. For example Cntrl-Alt-2 returns just 2. Not sure if that matters but I had to come up with something!

Are you planning on supporting G-keys? I unbound a key on my G13 it was not recognized.

I tried my best to trip up the typing but it was able to keep up with me.

[Freddie]

Under last action key name it shows what was last depressed and not a series of keys. For example Cntrl-Alt-2 returns just 2. Not sure if that matters but I had to come up with something!

I don't know either but I'm planning to add an option to make "Your last action" scroll, so that instead of each new action replacing the previous one, you can scroll up and see a history of what happened. I put that in HotkeyNet 2 and it came in handy a few times.

Are you planning on supporting G-keys? I unbound a key on my G13 it was not recognized.

Mojo responds to all key codes that the G13 sends to the operating system. (That's true for all hardware.)

But Mojo ignores all signals that the G13 sends to its own driver or its own user mode software. (That's also true for all hardware.)

I don't own any Logitech devices but if you unbind keys and then see nothing in Mojo's "Your last action" window, that means the G13 isn't sending anything to the operating system. It wouldn't surprise me if you have to assign an output key code to a G13 button in order to make the button send something to the operating system.

I tried my best to trip up the typing but it was able to keep up with me.

That's good news. It's amazing how fast computers are today.

[Freddie]

I got nervous after the conversation with Flekkie and Maxion about repeated key-down's because there is a slight difference in Mojo build 2 between the signals that Mojo sends to indicate an automatically generated key press and the signals sent by the operating system.

I'll get a little technical here for a minute in case anybody is interested. When the operating system sends a WM_KEY* message it sets or resets the 30th bit to indicate whether the key was previously pressed or released. Microsoft calls this the "previous key state" bit. When the receiving program (in this case WoW) receives a WM_KEYDOWN message it can inspect that bit to see whether the key press was generated typematically (i.e. automatically by the keyboard) or manually by the user's finger. This works because a typematic key press is always preceeded by a key down, but a manual key press is always preceded by a key up.

I didn't bother to set that bit in Mojo build 2. As a result of this thread, I just added stuff to the program to set that bit exactly like the operating system does. This will be in Mojo 3 tomorrow.

The only visible sign of the change will be a slight addition to "Your last action." The last line shows the status of the bit.

Thanks Flekkie for bringing this to my attention.

[Fizzler]

I don't own any Logitech devices but if you unbind keys and then see nothing in Mojo's "Your last action" window, that means the G13 isn't sending anything to the operating system. It wouldn't surprise me if you have to assign an output key code to a G13 button in order to make the button send something to the operating system.

I know in ISBoxer this works. If you unbind or do not assign any key to a G-key it is still passed. There is a thread about it. Perhaps I am doing it wrong I have all my keys assigned so I do not worry about it.

[Freddie]

I know in ISBoxer this works.

It could work in Mojo too if I wanted to spend time adding code to read Logitech's proprietary signals, but I've got too many other things to do that are more important.

I was telling you a design decision, not a statement of what's technically possible.

I said Mojo will *ignore* Logitech's proprietary data. I didn't say it's impossible to read the data.

If people want Mojo to work with Logitech's hardware, or any other hardware, all they have to do is set the hardware to send standard key codes to the operating system.

For me to spend a lot of time so people don't have to bother setting their Logitech with Logitech's software, when the end result will be exactly the same either way, doesn't make a lot of sense to me.

[Fizzler]

I do not use the G -keys myself I set up key codes just for the reason you mentioned proprietary nature.

Looking good so far.