Build 11 -- Hotkey triggers

[TheFallenOne]

That was the first thing I tried but it doesn't work for at least three reasons..

1. The user may want to enter Shift instead of LShift or RShift, and there is no Shift key. Same for the other modifiers.

2. The user may want to enter mouse buttons, but at least one button can't work that way because at least one button has to be "meta" to the entry field for navigation in the dialog box.

3. The user may want to enter keys that don't exist physically on the keyboard. (There are many dozens of such keys.) This is very useful when making hotkeys that get triggered by other programs or hardware devices.

What I've thought of doing is making two dialog boxes, a simple one that works the way you say and the current one. The simple one would come up by default, and it could contain a button that brings up the second one.

But even if I end up doing that, this first dialog box needs to be tested and improved and debugged.

I definitely think you should do this, setup two dialog boxes (manual selection and key press detection). It would definitely make things a lot easier to work with.

Great work so far, let us know if there's anything above and beyond testing you could use help with!

[Freddie]

I definitely think you should do this, setup two dialog boxes (manual selection and key press detection). It would definitely make things a lot easier to work with.

How do you know it would be easier? Have you tried this one?

You can type keys directly into this one. It does see your key presses.

Has anyone here tried this one?

Edit: I'm getting the impression that almost nobody here has tried this dialog box. Are people assuming that because the fields have triangles on them (they are comb box controls), you can't type into them? You can type into them.

[Freddie]

Just Checked the Dialog box out, Am I correct in assuming (I hate to assume But the jest I got was) this is only a test of the menu and nothing is actually being stored yet from the dialog box.

That's correct.

It definitely appears that we will be ably to have enough combinations to get the job done.

Yes, especially if the user is willing to "sacrifice" some keys to be used as modifiers. In that case the number of triggers is many millions.

My one question, (since you have stated before you would like to keep the average user out of the mojo directory)
are you planing a way for users to see what Hotkeys have been set in the past, by maybe graying out an established key combination and or give waring if were about to overwrite an existing key combination with one thats already established?

Yes, any time the user enters a setting that could inadvertently affect a different setting, the program will issue a warning.

If you try this dialog box and look at the many warning messages it generates, I think you'll see that I'm pretty compulsive about checking the user's input and warning about potential problems.

[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.
• 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.

[Freddie]

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.

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.

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.

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.

[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 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?

[Freddie]

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.

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.

[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.

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 )

[Freddie]

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.

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.

[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.

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.