I'm worried that some of my observations are a bit nit-picky, because I want to re-iterate that the overall impression for me was very good! In terms of its basic function I have not been able to break it yet, so it seems functionally sound.
I don't necessarily want to distract you from the core programming (unless you want me to).
I also thought the triggers help page was very clear and well written.
Anyways, onto the niggly things I thought of..
'Typing in' the mouse-clicks
It's a bit of a pain going through the list to find 'LButton'. I wonder if the mouse buttons could be grouped at the top of the list (since they cannot be 'typed' into the drop-box)? (Also liked the suggestion to group other keys instead of listing alphabetically.)
Alternatively, is it worth considering a 'Click area' to click on in order to input mouse clicks? Would that avoid the needing-a-meta-button-to-navigate-the-window problem?
I couldn't see such it in the list of controls here http://msdn.microsoft.com/en-us/library/aa511482.aspx but I know that such a thing exists. If you look in Control Panel -> (Hardware and Sound) -> Mouse -> Buttons Tab -> Double Click Speed Section then you can see such an area to test the mouse double-click speed.
Clearing
The clear all button is very nice. I wonder if it would be easy/appropriate to be able to clear a single drop-box and leave the rest? Probably the easiest way would be to have the very first drop-down option be a blank/clear option?
Setting up ranges of hotkeys
One of the nice things about scripts (in HKN) is that you can set up a range of hotkeys very easily.
I can still see a need for this even with a broadcasting option also available. For example, setting up FTL systems where input is a defined hotkey, and output is decided per %Trigger% and per window. (Windows = Wows according to Mojo's screens I think?)
I was curious if you wanted to give users the ability to set up ranges by using the GUI, or keep it to scripts? However, I won't try thinking up how to do that unless you need the input.
Max # of keys registered at once
[Edit: Sorry, scratch this section, you already covered it on the triggers help page! ]
My keyboard will not register more than 4 keys being pressed at once. If I hold down 4 keys and press a fifth key on the same keyboard, it does not transmit it. (I am pretty sure this issue is keyboard/input-device specific, but going by memory.)
However, the screen still lets me set up chords of more than 4 keyboard keys.
It's probably a non-issue, because why on earth would someone set up a longer chord? I really don't know if there are keyboards/input-devices out there which restrict below 4.
I can't really think of a solution either. Not without bumping into the LShift/RShift/Shift issue or the entering keys that don't exist on the input device issue. Best to ignore maybe?
The NumLock issue
This might be the wrong thread to bring this up. In a nut-shell, in order to set up a standard keyboards numberpad for hotkeys to work 'the same way' regardless of numlock state, I have to set it up twice (eg I would have to set up NumpadUp and Numpad8 both as separate hotkeys but which do the same thing).
Again, this might be easiest/best just left as it is. I was just wondering, in case there were any ideas kicking around to make this type of thing easier.
Connect With Us