Build 11 -- Hotkey triggers

From testing:

• If I press lctrl + lalt + lshift together simultaneously (or as near to it as I can), mojo only sees one of them as being pressed. If I press them more slowly, it sees all of them.
  Not sure if this is something you can, or want to, fix.
• When I press the same key twice, mojo let's me know (You entered X twice. That will have to be changed.) I would suggest at this point you remove the last duplicate key, so the user can hit the new one straight away, rather than now having to use the drop downs, or clear and start over (just realized you can click into the last input box and continue typing, but I still think clearing the last key would be better).

Will continue testing.

Edit: The 'Released' option for hotkeys is grayed out. I assume this isn't ready yet?

I completely admire you for doing this Freddie. Hotkeynet is amazing, I can barely imagine what this program will be capable of.

This looks very interesting.

When I hold down Left Mouse and another key say H. The input box shows the H highlighted in blue. I get the same when I do a Right Mouse and hold a key down. Is this on purpose? Is that how a Left Mouse key would look in the input box?

I read the help page, I am trying to understand exactly how this works and what uses it would have. If I create an input of <capslock> Rshift M if I hit that input what would happen? would a keymap or bind in the game be triggered? or would this be something specific to Mojo?

Issue: Pressing shift and a numpad number results in 3 buttons: Shift, NumpadEnd (number converted by shift), and shift again (which now gives an error). I know with windows generally you can't use shift with numpad, I don't know how you want to handle that.

Slightly unrelated to hotkeys.

Freddie, after the program is installed, going into 'Show License Dialog' still gives Accept and Decline buttons. Surely you can't decline after you've already installed the program (although I suspect declining doesn't even do anything yet at startup either :))

Suggestion regarding the 'Your last action' window and mouse motion.

As it is now, moving the mouse overwrites whatever the last action was. Also, if you want to determine a point on the screen, and then write it down, you need to make sure you mouse doesn't move from the point, otherwise you lose the location.

So my suggestion is this:
Between the 'Your last action' and 'Connections' windows, have a smaller window for Mouse motion. This will always have the current scrn and win mouse positions. Then also show these positions in the 'Your last action' screen, if the last action was a mouse button press (similar to Hotkeynet), and don't overwrite them until another key is pressed.

Sorry for chain posting, but I'm always reluctant to edit posts after some time has gone by, since someone replying might miss the edit.

Quote:

---

Originally Posted by Pocalypse

From testing:

• If I press lctrl + lalt + lshift together simultaneously (or as near to it as I can), mojo only sees one of them as being pressed. If I press them more slowly, it sees all of them.
  Not sure if this is something you can, or want to, fix.

---

I think I can do that but it will take a bit of work so didn't try yet. (All key events and mouse events are getting intercepted by Mojo's keyboard hook, they aren't getting handled normally by the dialog box code). I'll try to do this in the next build.

Quote:

---

When I press the same key twice, mojo let's me know (You entered X twice. That will have to be changed.) I would suggest at this point you remove the last duplicate key, so the user can hit the new one straight away, rather than now having to use the drop downs, or clear and start over (just realized you can click into the last input box and continue typing, but I still think clearing the last key would be better).

---

Good idea, I'll clear it in the next build and we can see how that looks.

Quote:

---

Edit: The 'Released' option for hotkeys is grayed out. I assume this isn't ready yet?

---

Right. It might seem strange that I bothered since this dialog doesn't really do anything anyway. But actually the dialog is building the data structure that will get used "for real" by the keyboard hook to determine whether the keyboard state matches a defined trigger, and I didn't build "press" or "release" into that data structure yet.

Quote:

---

I completely admire you for doing this Freddie. Hotkeynet is amazing, I can barely imagine what this program will be capable of.

---

Thanks, I really appreciate that. :)

Thanks very much for the suggestions here, this kind of feedback helps a lot.

Quote:

---

Originally Posted by Fizzler

This looks very interesting.

When I hold down Left Mouse and another key say H. The input box shows the H highlighted in blue. I get the same when I do a Right Mouse and hold a key down. Is this on purpose? Is that how a Left Mouse key would look in the input box?

---

I think that's Windows's default behavior. I haven't tried to alter it yet. You can select LButton from a list by clicking it with the mouse. You will see "LButton" in the field.

Quote:

---

I read the help page, I am trying to understand exactly how this works and what uses it would have. If I create an input of <capslock> Rshift M if I hit that input what would happen? would a keymap or bind in the game be triggered? or would this be something specific to Mojo?

---

Both. Anything.

Mojo is not only a broadcasting program (like other multiboxing programs) and a KM program (like Input Director or Kavoom) but also a hotkey program. That means you can define hotkeys and tell Mojo to do anything you want when you press the hotkey. There will be a programming language that you can use to describe what you want Mojo to do when you press a hotkey.

I'll probably also use this dialog box (or a similar one) to automate (as much as possible) the process of creating FTL keys etc. for WoW.

I think people will tell me what they want to use this for as the test goes on. :It will find a lot of uses.

Quote:

---

Originally Posted by Pocalypse

Issue: Pressing shift and a numpad number results in 3 buttons: Shift, NumpadEnd (number converted by shift), and shift again (which now gives an error). I know with windows generally you can't use shift with numpad, I don't know how you want to handle that.

---

Wow, you're really testing. :) Thanks. If I can think of an easy way to stop that I will.

Quote:

---

Freddie, after the program is installed, going into 'Show License Dialog' still gives Accept and Decline buttons. Surely you can't decline after you've already installed the program (although I suspect declining doesn't even do anything yet at startup either :))

---

It's like that because it's on the Debug menu. Anything on the Debug menu is only there for testing. It's not a real part of the program. Since this is a GPL program I'm not sure whether that license means anything at ll. I'm hoping a lawyer will come along and tell me during this test. :)

Quote:

---

Originally Posted by Pocalypse

Suggestion regarding the 'Your last action' window and mouse motion.

As it is now, moving the mouse overwrites whatever the last action was. Also, if you want to determine a point on the screen, and then write it down, you need to make sure you mouse doesn't move from the point, otherwise you lose the location.

So my suggestion is this:
Between the 'Your last action' and 'Connections' windows, have a smaller window for Mouse motion. This will always have the current scrn and win mouse positions. Then also show these positions in the 'Your last action' screen, if the last action was a mouse button press (similar to Hotkeynet), and don't overwrite them until another key is pressed.

---

A number of people have asked for this. If that keeps up I'll do it. The reason I did it this way is because mouse movement is an input to Mojo, so if the last thing a person did was move the mouse, then the last action was mouse movement. But if people want it changed I'll do it.

Quote:

---

Sorry for chain posting, but I'm always reluctant to edit posts after some time has gone by, since someone replying might miss the edit.

---

No problem, I think it's a good idea.

Makes it easier for me too because somtimes I overlook things in long posts. This way I'm more likely to see everything you say.

Looking good Freddie

I have a suggestion

The dialog box is awesome for defining hotkeys though i don't mind the scripting actually I kind of enjoy it
It gives me a sense of accomplishment when i script a long action or multiple actions for a hotkey like my log in script i like to figure out how to make it work like I want it to

Anyway to the point I suggest that when the dialog box is opened that a secondary text window opens that is a listing of the current hotkey definitions

You could make this very user friendly easy for a non coder to read
something like a a set of columns one for the hotkey trigger and one for the output

something like


Hotkey = output

Code:

---

_________________________________________________________________________________
Hotkey                |          Output                                        |
_______________________|_________________________________________________________|
Shift alt apps        |  Launch 5 wows and rename the windows                  |
                      |  Resize and reposition the windows                    |
_______________________|_________________________________________________________|
Rctrl 1                |  key 1 sent to all wow windows                        |
_______________________|_________________________________________________________|
Lctrl 1                |  key 1 sent to active wow window only                  |
_______________________|_________________________________________________________|
Ralt  1                |  key 1 sent to non active wow windows                  |
_______________________|_________________________________________________________|
Lalt  1                |  key 1 sent to specified wow windows wow1 wow2 wow4    |
_______________________|_________________________________________________________|

---

Or something similar

I think I need a visual of the existing keys while i use the dialog box to edit the "script"

New build

A new build (12) is up. Based on what people said here, I made three changes.

1. It's now possible to press a bunch of keys simultaneously and they all get entered. They don't have to be entered one at a time.

2. There are now instructions, a line of text above the entry field that says, "Press keys or select from list with mouse."

3. If you enter a duplicate key, the field now becomes blank and that field retains the focus after the message box is closed.

Thanks very much for the suggestions.

I'm very curious to know whether people think change 1 eliminates the need for a second easy-mode dialog box.