Build 11 -- Hotkey triggers

[airlag]

Hi, nice to see you here
I use HKN for a while now. Of course I'd like to see Mojo being as mighty as HKN. Don't kill me for asking too much with my first posting

So here is my suggestion for improvement:
We have basically 3 types of keys

1) Hotkeys - trigger once when pressed or released. Maybe 2 different actions when possible? You already need 2 actions for just mirroring a standard keybord action, key down and key up. So it would be natural to allow free programmed actions on pressing/releasing a hotkey.

2) Modifiers - "natural" modifiers are capslock, scrolllog and numlock. It would be nice to define modifier keys freely. I made capslock of the keyboard to a normal hotkey to prevent SHOUTING ACCIDENTLY AT PEOPLE IN CHAT. I made pause to a modifier that pauses HKN. You see what I mean. If you implement this you need to create the "Execute the hotkey only when" section of the above window dynamically.

3) Movement keys - are special in HKN, but with 1) fully implemented they are only a subclass of Hotkeys. Instead you may need a key repeating trigger (delay and repeat time freely defined for every repeating hotkey). That would be an improvement of Hotkey triggers again

[Freddie]

1) Hotkeys - trigger once when pressed or released. Maybe 2 different actions when possible?

Both HotkeyNet and Mojo can perform millions of actions when you press or release a key. But the key can only be pressed or released because that's all a key does. The key can only be pressed or released because that's how they build keyboards at the factory.

Pressing or releasing a key is input. What Mojo does is output.

Most of your comments here about about output -- what Mojo does. This dialog box is only about input. This dialog box has absolutely nothing to do with output.

So it would be natural to allow free programmed actions on pressing/releasing a hotkey.

HotkeyNet does this and Mojo will also do it. It's going to have a powerful programming language, much more powerful than HotkeyNet's.

2) Modifiers - "natural" modifiers are capslock, scrolllog and numlock. It would be nice to define modifier keys freely.

Edit: I misunderstood this because you're using "modifier" in an unusual way. "Modifier" usually means Shift, Ctrl, or Alt. The three "lock" keys don't have a name, so I call them lock keys.

These three keys generate states that are built into the computer. If you have a desktop keyboard you can see that these three states are built into the computer because the keyboard has LEDs for them. These three states are *input* to Mojo because they are external to Mojo.

You will be able to create additional states with Mojo, just like you can with HotkeyNet, but additional states are output. They are something that Mojo does. This dialog box is only about input, things that are given to Mojo.

As for "modifiers" in the normal sense of the word (Alt, Shift, and Ctrl), Mojo can use any key as a modifier now, and if you play with the dialog box you will see that it accepts any key as a modifier. This is explained on the documentation page I linked at the bottom of my previous page.

I made capslock of the keyboard to a normal hotkey to prevent SHOUTING AT PEOPLE IN CHAT. I mad paus to a modifier that pauses HKN.

You will be able to do that sort of thing with Mojo. If you think this dialog box limits that, you are misunderstanding it.

You see what I mean. If you implement this you need to create the "Execute the hotkey only when" section of the above window dynamically.

No, the section doesn't need to be dynamic to allow those features. That section corresponds to states that are built into the computer. Mojo's abilities are not limited to what is built into the computer.

Once again, this dialog box is only about input, i.e., things that are external to Mojo, i.e., the keyboard.