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

[Flekkie]

5. Broadcasting was changed slightly to ensure that when Mojo broadcasts automatic repeated keypresses that are generated by a keyboard, WoW receives *exactly* the same signals that it would receive from the keyboard itself. As part of this change, Mojo now displays "prev state" in "Your last action." This means "previous key state," i.e., the state of the key before your last action.

Thanks Freddie, I really appreciate that.

6. The scrolling code from the main window was rewritten to try to eliminate reported flicker. You can select "Test" under "Debug" on the main menu if you want to see the window scroll indefinitely at 33 messages per second.

TBH, I wasn't so worried about the flicker, more about the autorepeats. The flicker actually served its purpose by indicating the autorepeat to me.

It still flickers, just a bit less, but I am quite happy about it as a user.


Shortcuts and finding the program
I accidentally deleted my desktop shortcut, and had to search my C drive to find where Mojo had hidden itself. It was not in the C:\Program Files (x86) folder as I expected, but in C:\Users\MyLogonName\App Data\.. and so on. The App Data directory is a hidden directory! So very hard to find.

Also, the shortcut doesn't behave like a normal shortcut when I right-click it; there is no description of a target path or compatibility tab.

Not a problem for me, but just to flag it up to start thinking of ways to make it easier for Joe Public.


Security alert
Got the Windows security alert again. Oh well, it's just the built-in firewall doing its job. It correctly identified the software as Mojo so you twiddled the right knob for that.


Stress Test (1 PC only)
Performed the test as requested, but I only have the one PC so bear that in mind.

I opened 30 WoW windows. With no CPU core allocation, they were all stuttering a bit to start with. Then I started the menu option Debug -> Test, focused a WoW window, and Shift-Tabbed to the 'account name' field, and typed something like "This IS A Test" at normal typing speed (no, I am not a typing master!).

The results on each of the 30 windows was not uniform. The letters were correct and in the correct order. However their shift states were slightly different in each window. It was not the same error in some, but various different errors across most.

From this I suppose that Mojo is sending the key downs and ups, but not specifying what order to perform them in? I wonder if there would be a hit to performance to ensure actions are performed in a sequence? I can think of several ways to do it, but most would probably be wrong since I know nothing about the actual mechanisms in play. Or maybe I have guessed the wrong cause.

Oh yes, and as someone else mentioned, I had to quit Mojo in order to stop the test.


Mojo's Actions Pane / Log / whatever its called !
I have started to form some ideas about the "Mojo's actions on this PC" frame. Would you like me to start a separate thread on it, or add them here?