Hotkeynet comming back?

[Freddie]

Come to think of it, HKN already has a feature almost exactly like that. You can define commands that are triggered by strings of text like this:

<Command MyCustomCommandText>
<sendpc local>
<sendwin blahblah>
etc.

Right now when you want to invoke that command, you input the text to HKN with HKN's command line window, but I could very quickly add a new hot key function that allows the Nostromo to type the command text directly into HKN the way I described for numbers in the last post.

This would give you (aside from memory constraints) an infinite number of hotkeys, because the length of the command text is unlimited.

(If you wanted to use this on a large scale I'd probably have to rerwrite the code that interprets the command names and make it much faster. Right now it just does a bunch of strcmp's, and I've never tested it with more than 3 or 4 commands.)

But again, I'm wondering, how do you input all these thousands of commands into the Nostromo to begin with? The more I think about this, the more it seems like the bottleneck is there, not in HKN, but maybe I'm missing the whole point.

[Freddie]

Maybe I just figured out what you mean. Do you want to tap a key that means "The next hotkey should be sent to Client X." then you tap something that invokes a hotkey whose definition, by itself, doesn't designate any particular window. When the hotkey executes, it takes its target from the target that was picked by the previous key tap.

Is that it? If so, I dont think this is a matter of modifiers. I think it has to do with adding some kind of state variable to HKN so it remembers from one hotkey to the next what the desired target is. Right now HKN loses its memory completely between hotkeys.

it would work like this:

<Hotkey F1> // F1 will direct commands to WoW 1
<sendpc local>
<SetDefaultTarget Wow1>

<Hotkey F2> // F2 will direct commands to Wow 2
<sendpc local>
<SetDefaultTarget Wow2>

<Hotkey F3> // output will go to whatever was picked with previous hotkeys
<SendWin %DefaultTarget%>
<text blah blah blah>

Is that what you were thinkikng of?

[Basilikos]

Freddie,

Like I said, there is a very strong likelihood that I have just not thought through all the possibilities. I'm currently taking advantage of the fact that HKN does differentiate between left and right keys to send commands to all four slaves. I do have keyboards attached to the two slave machines, so that is definitely useful. I will need to check on whether or not the Nostromo software supports left and right differentiation on all modifier keys (I'm certain it does on SHIFTs, but I don't recall the others).

To answer your more specific questions, right now I have 1-0, -, and = bound to three hotbars inside my main WoW client. The first bar is accessed simply by the stated keys. The second is accessed through the named keys and the left shift button. The third is accessed through the left alt key and the stated buttons. The pet and shapeshift bars are accessed through either CTRL and 1-0 or CTRL+ALT+1-0. What I was looking for was an easy way to specify a specific client that should receive the command from the N52.

I'll look over things again and see what I can get going. The real issue is going to be overlapping combinations of CTRL or ALT+CTRL (or similar combinations) and whether or not the Nostromo software recognizes left vs. right everything.

Thanks for all the attention you give the community here.

[Freddie]

Did you read my last msg? I think all the earlier ones probably missed the point.

[Freddie]

*roar*

Bah, blue is so boring. Red ftw!!!

[Draku]

I just did the dailies (about 2 hours) using Hotkeynet and using movement keys for formation and for initiaiting flying (ie going up at start), works perfectly.....

[Freddie]

Woot! Thanks for letting me know.

One sad thing though -- I just rewrote Key, KeyDown, and Keyup. So they all have to be tested again. ;(

You already know this but for other folks, I did it to make them 100% consistent with each other. Now they have the same syntax and call the same code.

[Basilikos]

Maybe I just figured out what you mean. Do you want to tap a key that means "The next hotkey should be sent to Client X." then you tap something that invokes a hotkey whose definition, by itself, doesn't designate any particular window. When the hotkey executes, it takes its target from the target that was picked by the previous key tap.

Is that it? If so, I dont think this is a matter of modifiers. I think it has to do with adding some kind of state variable to HKN so it remembers from one hotkey to the next what the desired target is. Right now HKN loses its memory completely between hotkeys.

That is pretty much the behavior I was looking for, but I think this solution presents problems to me that I'd rather avoid.

I'd like whatever key(s) I use for these "per-client" modifiers to be just like any other modifier. I don't want any state to change based on what key I just pressed. If I decide split-second not to take whatever action I was considering, I don't want to have to worry about what client I just selected; I'd really rather just take my finger off the key and have things be as they were.

Like I said, I'm still looking into how the Nostromo handles left or right modifier keys.

[Freddie]

That makes sense. Also it occured to me after I posted that idea that when you assign any unmodified key to be a hotkey, like I suggested for the state change hotkeys, they get just as "disabled" for other purposes as they would if you made them modifiers.

I had a few more ideas but I wonder, could you describe with some concete examples what keys you would like to press, ideally, for this? And would you press them on the Nostromo or the PC? How many keys do you want to press at a time? etc?

[Basilikos]

...could you describe with some concete examples what keys you would like to press, ideally, for this? And would you press them on the Nostromo or the PC? How many keys do you want to press at a time? etc?

Certainly. For starters, I was only going to use the numpad keys to direct where the other key presses would go (NUMPAD0 would be a general broadcast to all slave clients, NUMPAD2 to the second client, and like that up through NUMPAD5 to the fifth client). The rest of the key presses were going to occur on the Nostromo and these key presses already used some SHIFT, CTRL, and ALT modifiers (and sometimes, ALT+CTRL and other combinations). And before I forget, there were a few other keys (ESC, B, SPACE, etc) that I had on the Nostromo as well besides the 1-0 (and -,= depending on the bar we're talking about).

The idea was that I could keep all the functionality I had on my main AND use the same controls on the slaves (either individually or as a group). Right now, I'm using the RSHIFT as a general broadcast modifier. If memory serves, the Nostromo software doesn't differentiation between the left and right CTRL and ALT keys (well, it might for ALT). If it did, I could just alter the script I use to output all of the hotkey definitions and load them into HKN.

And on another note, the Nostromo and HKN get along pretty well. HKN is able to see and capture the appropriate events nicely.

In general, I don't think I'll press more than 4 keys at a time (the client modifier, two regular modifiers, and some other key be it numerical or alphabetical).

Did I get everything?

Thanks.