Build 16: Alt-tab bug fixed

[zenga]

The two of you should team up and start a business. Seen many situations where large projects would die to get a coder and dedicated tester with such an interaction

[Freddie]

thx.

I spend a good hour or two last night trying to break it (lots of alt-tabbing and other weirdness) - no issues.

Great.

So what's next?

Like Zenga says, let's get rich!

Let me try to remember recent requests.

The next thing on your list was keymaps. I think the next thing on Moorea's list was no-pass. That's sort of the same, right?

I might have to do "launch WoW" before keymaps make much sense.

Other people asked for visible cursors, status overlays, um, what else.

Edit: mouse broadcast.

Edit: Set a PC not to receive incoming (as opposed to the existing mode buttons and hotkeys which all affect outgoing).

Edit: re-enable WoW window and finish the code that tracks scheduled and running WoWs.

Edit: Triggers need to be finished. They don't yet include an option for "trigger when key is released" and "allow or disallow typematic presses to trigger this hotkey."

Edit: There are two remaining bugs on the bug list but I'm inclined to leave them for now since they will be a pain in the ass and nobody has complained about them.

Moorea, if you're reading this, you know what would help me in the FAQ? If you could figure out some way to include a running summary of requests with a count of how many people asked for each one. A top-ten requests list. Right near the beginning of the FAQ.

Does the word "keymap" come from Keyclone? Can someone post a screenshot of what a keymap config screen looks like so I have a better idea of what's being requested?

[zenga]

The next thing on your list was keymaps. I think the next thing on Moorea's list was no-pass. That's sort of the same, right?

How i see it is that keymaps and don't pass are essential functionalities for a boxer and it would take mojo to the next level.


Keymaps: e.g. map ctrl+A to jump on toon A and B and move forward on C while both ABC have exactly the same ingame keybinds

Do not pass: respective keypresses are not passed to all clients, only to the active window. If we could decide to which clients it should be passed and to which not, would even be more awesome. For example i have my arrow keys set as main movement keys on all clients and i have ZQSD as my secondary movement keys on my slaves (not on my main). The arrow keys are not passed to slaves. This means i can just move around with my main with the arrow keys and have my slaves on follow. If i need to move my slaves out of a puddle in a bossfight, i just use ZQSD. On the other hand if i switch to a slave i can just use the arrow keys to move around like i'm used to without my alts responding.

[UNIXman]

Liking Mojo, a lot.

In case it wasn't suggested, would like to see:

• Broadcast window and mouseover at the same time.
• The option on whether or not to send certain keys (like movements keys, on WoW) is really needed to completely replace HKN.

[ElectronDF]

My request from the past that started the whole lot of something was a key to HOME the mouse pointer. So when you are doing mouseover, you can push a key to cancel it and put the mouse back in the middle of the main screen. It doesn't have to be middle, just it takes like 10-15 secs to find out where my mouse was, move it to the main screen, move my head back to main screen (multiple computers) and then figure out what is going on. It would make me happier to just push "SOMEKEY" and bam, back on main screen and ready for anything. I like to mine and herb on my alts, so when I come to an item, I want, I need to use my alts mouse to get the item. But the best items are in PVP zones. So when I land and get the item, people want to attack me. So I have to be ready for attack and getting items quickly.

[Freddie]

My request from the past that started the whole lot of something was a key to HOME the mouse pointer. So when you are doing mouseover, you can push a key to cancel it and put the mouse back in the middle of the main screen. It doesn't have to be middle, just it takes like 10-15 secs to find out where my mouse was, move it to the main screen, move my head back to main screen (multiple computers) and then figure out what is going on. It would make me happier to just push "SOMEKEY" and bam, back on main screen and ready for anything. I like to mine and herb on my alts, so when I come to an item, I want, I need to use my alts mouse to get the item. But the best items are in PVP zones. So when I land and get the item, people want to attack me. So I have to be ready for attack and getting items quickly.

This was done a couple of builds ago. You need to set a trigger from the Settings Menu : Predefined Hotkeys.

That reminds me, I have to make it possible to set the trigger from the Mousever screen.

Instructions here:

http://www.mojoware.org/help/predefined_hotkeys.html

[Freddie]

Liking Mojo, a lot.

In case it wasn't suggested, would like to see:

• Broadcast window and mouseover at the same time.

This is now enabled in build 18.

I also re-enabled the WoW button. You'll see some stuff that isn't finished.

[Freddie]

Keymaps: e.g. map ctrl+A to jump on toon A and B and move forward on C while both ABC have exactly the same ingame keybinds

Could you please clarify that for me? For any trigger, there are three things involved:

-- the key or key combo that's pressed by fingers physically

-- the key or key combo that Mojo sends to WoW

-- the in-game action .

Could you restate that example in terms of those three things?

Do not pass: respective keypresses are not passed to all clients, only to the active window. If we could decide to which clients it should be passed and to which not, would even be more awesome. For example i have my arrow keys set as main movement keys on all clients and i have ZQSD as my secondary movement keys on my slaves (not on my main). The arrow keys are not passed to slaves. This means i can just move around with my main with the arrow keys and have my slaves on follow. If i need to move my slaves out of a puddle in a bossfight, i just use ZQSD. On the other hand if i switch to a slave i can just use the arrow keys to move around like i'm used to without my alts responding.

That will definitely be in the program. That's why I said above that I might have to do "launch WoW" before no-pass. The program will need to launch WoW in order to provde the user with config screens that refer to individual WoWs.

[Freddie]

Be sure to include "ActiveWindow" and "!ActiveWindow" in your options - Sometimes I mouse over to a slave machine and start playing from there, and I would love it if it just mapped my keys accordingly.

Definitely, the program should provide these options.

The problem is designing an interface that makes it easy to choose. Do you have any ideas about that?

PiP, and PiP "Positional Awareness/Preference" - the second part is a little difficult to explain but let me try:
In Octopus I have 2 screens setup - 4 WoWs in a 2x2 config and 1 WoW that takes the whole screen. If I have the WoWs configured as:
A is Main Screen
B is Top Left Secondary Screen
C is Top Right Secondary Screen
D is Bottom Left Secondary Screen
E is Bottom Right Secondary Screen
[B|C][AA]
[D|E][AA]

If I press the PIP button associated with B, it will swap A with B:
[A|C][BB]
[D|E][BB]
If I then press the PIP button associated with C, it will swap B with C:
[A|B][CC]
[D|E][CC]

The problem with this, is that I want B to either be Main or Top Left, I never want it to be Top Right (which is where it is now). I can get around this by ALWAYS pressing the PiP associated with A first and then the PiP assocciated with the WoW of my choice ... but I would rather it take care of that in the background so I can hit it quickly when I need to.
Since some people may not want this (because it means moving 2 screens sometimes, which may take longer) it would need to be an option that could be set either way.

Let me know if this is clear.

Yeah, it's crystal clear. People should be able to define keys that change their PIP setup in any way they want. That includes such things as defining which WoW's window goes where, which window-by-current-location goes where, conditions such as which WoW is currently in the foreground, etc. (And do this without using the script language. Of course users will be able to do anything whatsoever with the script language).

Do you have any ideas for how to design the interface where people create their PIP layouts and their PIP hotkeys?

I'd like to give people completely generalized choices, so there are a lot of permutations, but I'd also like the screen(s) to be extremely easy to use.

[Freddie]

What I try to do is push everything I know technically out of my head -- forget everything I know about the code -- and imagine using the program. Then I ask, "What would be the easiest thing to see on the screen and move with the mouse?"

The bad thing is, usually there's no answer.

The good thing is, my advancing Alzheimers makes it easy to forget what I know. I'm great at that part!