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

[Freddie]

This is a "revise" build instead of a "new features" build. It contains some changes that were suggested by conversations in other threads here.

1. You can now turn broadcasting off from the Actions menu. (Later there will be more convenient ways.)

2. Error messages and tracing have been added to both log files to try to diagnose the reported bug that makes the program fail to start.

3. A new item, "Debug," has been added to the main menu. It allows you to look at various things.

4. The installer''s security checking was disabled to see if this will have any effect on firewall messages (it probably won't).

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.

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.

[Freddie]

On second thought, I'd like to ask people to test something.

Start Mojo on two PC's.

Load a bunch of WoW windows on both PCs. Leave them at the account name screen and put the cursor in "account name" so you can see your typing.

Edit: You don't need WoW accounts for this. You can just launch WoW many times and leave it at the account name screen.

Select Debug : Test on both Mojos. This will put them under artificial stress.

Bring WoW to the foreground on one PC.

Spam keys as fast as you can on that PC.

See if the broadcast keeps up in all WoWs.

Thanks a lot!

[ElectronDF]

Minor note, my XP machines computer names are truncating the last char. Ex:
fullgames.FULL.loca
fullvideo.FULL.loca
My Win 7 machine shows as full name on all machines.
Not a big deal, just thought I would mention it.

[Freddie]

Thanks, I'll look into it.

[Freddie]

Minor note, my XP machines computer names are truncating the last char. Ex:
fullgames.FULL.loca
fullvideo.FULL.loca
My Win 7 machine shows as full name on all machines.
Not a big deal, just thought I would mention it.

I can't duplicate this, so I made a test build (number 4). Could you do me a big favor:

1. Run build 4 simultaneously on both machines.

2. Let it run for about 30 seconds on both machines.

3. On both machines, go to "Debug" on the menu and select "Show engine log."

(The reason for running only 30 seconds is that the engine log will very rapidly fill with repeated lines that we don't need.)

Could you either email me or paste here the engine logs from both PCs? .

Thanks a lot.

[Bettysue]

Running the test as stated in your post, I had 10 WoW clients running on each computer. The broadcasting of keys seemed to keep up quite nicely, with no noticeable lag at all.

The one thing I did see while taking advantage of the keyrepeating (hold a key down in this case Backspace) was that the computer with the keyboard being pressed it would fall behind the second comp. For example I could type 50 characters into the name box, on all of the clients (remote and local), and then hold backspace till all the characters were gone on the remote machine and the local machine would have a few characters left to delete.
I know you mentioned it somewhere but shifted keys did not send to the remote clients, ( @ ? ! < > etc. )

The download and install was phenomenal with no issues. Broadcasting worked only when "a" WoW window had focus, anything other than WoW would stop broadcasting. Broadcasting stopped when using the option in the menu as would be expected. Broadcasting even worked while using HKN2 and moused over to the remote machine, with no strange double key type stuff. (by double key I mean the local machine kb broadcasting the keys and the remote machine being controlled by the local kb sending a key. )

There is no way to stop the test other than to close the mojo window???

Anyway it's coming along pretty nicely by the looks of it, let me know if you need more details, or any other help...I'm usually around and bored


Edit: Wow it got better while i was testing it, I feel so outdated now, these dang computer machines are getting too fast for me :P

[Freddie]

Running the test as stated in your post, I had 10 WoW clients running on each computer. The broadcasting of keys seemed to keep up quite nicely, with no noticeable lag at all.

I'm glad to hear that!

The one thing I did see while taking advantage of the keyrepeating (hold a key down in this case Backspace) was that the computer with the keyboard being pressed it would fall behind the second comp. For example I could type 50 characters into the name box, on all of the clients (remote and local), and then hold backspace till all the characters were gone on the remote machine and the local machine would have a few characters left to delete.

Hmm, I wonder if that's due to an error. . Maybe, while you typed, some characters failed to reach the remote, so there were more characters to delete on the local. Do you think that might be the reason?

I know you mentioned it somewhere but shifted keys did not send to the remote clients, ( @ ? ! < > etc. )

Right, that's not done yet.

The download and install was phenomenal with no issues.

Great.

Broadcasting worked only when "a" WoW window had focus, anything other than WoW would stop broadcasting. Broadcasting stopped when using the option in the menu as would be expected. Broadcasting even worked while using HKN2 and moused over to the remote machine, with no strange double key type stuff. (by double key I mean the local machine kb broadcasting the keys and the remote machine being controlled by the local kb sending a key. )

Great. That's all as intended at this early stage. It's just a barebones implementation of broadcasting to make sure the basic code works right. I like to do things one step at a time and try to get each step right before the next.

There is no way to stop the test other than to close the mojo window???

Right, I just added it to the program temporarily to see if the new scroll code works properly. I wasn't even planning to mention it here. But then it occurred to me, after posting the build, that it's a decent stress test. Maybe I'll add an off switch and keep it in the program for the rest of the alpha/beta test.

Anyway it's coming along pretty nicely by the looks of it, let me know if you need more details, or any other help...I'm usually around and bored

That's a great offer. I'll take you up on it. If you're interested, it would probably help me to work interactively with somebody, maybe even talk on the phone.

Edit: Wow it got better while i was testing it, I feel so outdated now, these dang computer machines are getting to fast for me :P

It's incredible isn't? It just amazes me how fast my slow crappy code is running!

[Bettysue]

Hmm, I wonder if that's due to an error. . Maybe, while you typed, some characters failed to reach the remote, so there were more characters to delete on the local. Do you think that might be the reason?

Yes now that I think about it, it is most likely my computer, it was running an AV scan in the background trying again it doesn't seem to be duplicating the lost keys thing it was doing before.

Great. That's all as intended at this early stage. It's just a barebones implementation of broadcasting to make sure the basic code works right. I like to do things one step at a time and try to get each step right before the next.

Seems like a very good plan there's no point to building towers in quicksand.

That's a great offer. I'll take you up on it. If you're interested, it would probably help me to work interactively with somebody, maybe even talk on the phone.

That may be quite an expensive endeavor unless you have a VoIP phone or something along the lines of free telephony, as I currently reside in Korea...and they just so happen to have the same outrageous long distance bills the rest of the world does...damn capitalism

[Freddie]

Seems like a very good plan there's no point to building towers in quicksand.

That's a great metaphor. I'm going to remember that and repeat it when I explain to people why supporting HotkeyNet 1 has become a nightmare.

That may be quite an expensive endeavor unless you have a VoIP phone or something along the lines of free telephony, as I currently reside in Korea...and they just so happen to have the same outrageous long distance bills the rest of the world does...damn capitalism

Pay for phone calls? That's so twentieth century!

I like to use Skype for this ... it's free and it works quite well.

http://www.skype.com/

(Calls with Skype are free if both people are using it.)

[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?