Build 16: Alt-tab bug fixed

[Freddie]

?
What in-game WoW command?

Quoting from your drawing:

AllAttack
Heal1
Heal2
Heal3
Heal4
FrostNova

[Freddie]

Ah!

Those are user input "names" - there is no correlation to wow. AllAttack would simply be a friendly name the user gave something so they knew what it was. "FrostNova" isn't bound to "Frost Nova"...
There is nothing in WoW called AllAttack or Heal1...

Does that help?

Edit:

I just realized:

Your first screen defines the key(s) that the user presses with his fingers.

Your second screen defines the key codes that Mojo sends to WoW.

Is that right?

[Freddie]

Like I said, Many-to-many is always a difficult subject to wrap the brain around, let alone get an app to do it in a way users can understand.

When you open a folder and see a bunch of files, that's a one-to-many relationship. . One-to-many doesn't mean anything more complicated than that.

I have three daughters. They each have one father. That's a one-to-many-relationship.

The hard thing about designing a simple screen that lets the user map physical key presses to Mojo's output is that the user has to specify conditions under which different output gets generated. But specifying conditions has nothing in particular to do with one-to-many.

As Fur is saying start with Whitelist/Blacklist - that's the "master" and the bare minimum necessary to get a multiplexer working in a meaningful way. From there an "advanced" setting could be available to take the user into a config that would allow them to do the complex mappings. Marking it as "advanced" would have the advantage of detering users from that section that would really only get them into trouble.

Most of Mojo will probably be designed with progressive disclosure of increasingly complex features.

If you want to see an example that's already in Mojo, go to Connection Settings and click the first two radio buttons. Also see the "More options" button at the bottom.

(Microsoft advises software designers to say "More options" instead of "Advanced" because it's less intimidating.)

I just had an idea for a new feature request ... If I could just post a mojo.config file that will gracefully import on the user's end (so they don't have their settings lost, etc) then the community will quickly be able to assist on getting new users up to speed - even when there is a good deal of complexity

.

I think that's a good idea. The data structures and algorithms that are used for Mojo's config info have been designed to make it easy to remove a branch of config info from the overall tree and graft it onto some other tree, so this should be very easy to implement. .

[Akoko]

I've officially replaced Keyclone with Mojo. I love you!!

(Still have to use HotKeyNet to launch the windows though... )

[Freddie]

I've officially replaced Keyclone with Mojo. I love you!!

(Still have to use HotKeyNet to launch the windows though... )

, I can't believe it! It has so few features at this point. That's great.

It's very fun to hear this. It's a shot in the arm to crank up the compiler and work on it. Thanks.

Launch is coming soon. (It would have been today probably except I ran into a problem and have to rewrite some stuff. So it wil be a few days.)

[Freddie]

Funny note: Microsoft may "suggest" that you stay away from the word advanced... but even Win7 has an Advanced Find .

This reminds me. Some people might find this fun, and it could help.

Microsoft has a division that publishes design guidelines. It's a big document -- 800+ pages -- and it consists mainly of suggestions that have to be applied with judgment.

I usually try to follow it. If anybody wants to read it and help make Mojo stick to it better, that would be great.

Download at:

http://www.microsoft.com/downloads/d...3-1b9e8ea7fe8c