Build 11 -- Hotkey triggers

[Freddie]

I think Freddie has included these 6 states because they are hard-wired into any keyboard, or kept track of by the OS (he will no doubt correct me ).

You're exactly right.

The two people who brought up this issue are both HotkeyNet users, so let me add something from their perspective.

The dialog box that we're talking about here corresponds to the <Hotkey> statement in HotkeyNet.

The only things you can put in a <Hotkey> statements are (1) lock states (2) modifiers and (3) keys.

This dialog box is exactly like Hotkeynet's <Hotkey> statement. The six check boxes are the lock states.

HotkeyNet has a lot of other stuff besides the <Hotkey> statement, and Mojo will have a lot of other stuff besides this dialog box.

[rocnroll]

Something I have noticed is that ever so often Mojo will start flashing in the Taskbar. I seem to remember that HKN2 did the same thing. What is Mojo doing? It's mildly annoying, but certainly not a show stopper.

Oh, the overall progress is really good Freddie, I just need to do some more thorough testing.

[Freddie]

Something I have noticed is that ever so often Mojo will start flashing in the Taskbar. I seem to remember that HKN2 did the same thing. What is Mojo doing? It's mildly annoying, but certainly not a show stopper.

When does that happen? What are you doing when that happens?

(In general that flashing means that the program is trying to come to the foreground but the operating system won't let it.)

Oh, the overall progress is really good Freddie, I just need to do some more thorough testing.

Thanks.

[Freddie]

New build 13

I made some changes that people suggested including a new name for the dialog box.

I also changed the text a little bit to try to avoid giving people the impression that the lock checkboxes are the only things that will be in the program for toggling conditional states.

The main change is mouse buttons. You can enter them all directly now. Two questions:

1. LButton has to work normally in order to navigate around the dialog, so I decided to require a double click in order to enter it. Is this a good solution?

2. You can enter WheelForward and WheelBackward by turning the mouse wheel. Should this be disabled? I think it's confusing.

[Pocalypse]

1. LButton has to work normally in order to navigate around the dialog, so I decided to require a double click in order to enter it. Is this a good solution?

2. You can enter WheelForward and WheelBackward by turning the mouse wheel. Should this be disabled? I think it's confusing.

1. I like how LButton works.

2. On my Logitech MX mouse, this is incredibly frustrating. The scroll wheel is very sensitive, in that as soon as I try to use it once to input ScrollWheelUp, it sees multiple presses and gives me an error. Often it activates even if I don't want to enter a ScrollWheel button.

Also, am I correct in thinking that with this hotkey system, we can set up actions for left click while right click is pressed, or right click while left click is pressed? That could be really useful (I'm thinking of other things than WoW here, it probably won't be good to set those up for WoW because of the camera tilt with mouse buttons).

[Freddie]

1. I like how LButton works.

2. On my Logitech MX mouse, this is incredibly frustrating. The scroll wheel is very sensitive, in that as soon as I try to use it once to input ScrollWheelUp, it sees multiple presses and gives me an error. Often it activates even if I don't want to enter a ScrollWheel button.

Thanks for the feedback. The wheel is annoying for me too on a cheapo mouse. I'll probably change it after we hear from a few more people.

Also, am I correct in thinking that with this hotkey system, we can set up actions for left click while right click is pressed, or right click while left click is pressed?

Do you mean the user would press LButton and Mojo will send a signal to a game that makes the game think you pressed RButton?

Yes, that will be possible with hotkeys and maybe also with broadcasting. (Hotkeys can do everything that broadcasting does, so I don't know yet how much work I'll put into the broadcasting screens.)

The trigger (what you do with your fingers) is input. The action (what Mojo does when it sees the trigger) is output. They are completely different things.

By default, in Broadcast mode, Mojo makes its output match the trigger. For example, if you press A, the program sends A to games. This is what dual-boxing's Wiki calls "multiplexing."

But there's no reason why they have to match. The software generates the output by computation. The output can be anything.

[Pocalypse]

What I was thinking of are called rocker gestures, though don't ask me where that term is from, because I can't remember .
I'm thinking of holding down the right button and then pressing left button, or holding down the left button and then pressing the right button.
Hmm, I think firefox gestures are where I used these last.

The way the dialog is now, these will be possible to create. It's just a nice option to have.

[Freddie]

Oh, I see. I never heard of that, but it sounds great. Yep, this lets you do that.

Edit: The thing that prevents that in HotkeyNet is that it won't allow people to put a modifier at the end of a trigger. I'm trying to remove all the restrictions in Mojo.

[Aragent]

Freddie

I know you have talked about this back in HKN and HKN2 Development talks, And possibly already in the early stages of Mojo.
(If my memory serves correctly. These days i am not always sure it does)

Have you done any more Thought about having mojo be able to differentiate between 2 keyboards connected to the same pc,
thus allowing them to act as 2 seperate keypads ?

[Freddie]

About a year ago I wrote some test code to see what would be needed to implement this. I only found one way that it can be done, and it would increase the complexity of the program quite a bit and take a lot of work, so I don't think think this will be in Mojo any time soon.