[Keyclone] how to not get wiped when your main dies...

[Naysayer]

actually, i generally move with mouse and keyboard. i use my arrows for keyboard driving (which is in the DNP) and mouse otherwise.

i tie ctrl+LBUTTON via the mouse-map to ctrl+= (my '/follow focus' hotkey).. and just ctrl+left click when i'm ready to move. then left+right to drive

when it gets sticky, i have WASDQE available to move all characters at once (QE used most .. strafing == very useful)

Technically, I actually use an n52 nostromo speedpad and use the analog thumbpad to move(just like the ol' nintendo controller) and have that mapped to the arrow keys. It's the same as WASD, but you use your thumb for all four directions, and instead of using "turn" I use strafe for left and right. I turn/rotate view with my mouse, and use the fifth button on my mouse(thumb) as Shift so that I can double my N52 keys by binding them to the F1-12 keys and Shift+F1-12.

I highly suggest the nostromo thumbpad movement for those that are willing to adapt, it takes some time.

[Naysayer]

Would there happen to be a way to pass keys to the clones, but block those keys from being executed on the Main PiP? Say I wanted to add a couple keys to turn my alts left and right, but I don't want this done on the main. I could just hotkey it through WoW interface on the alts, but when I switch through my clones with PiP I'd have a problem.

It would be kind of like black-list do not pass, but work for all background windows and exclude the main. If you have any solutions, I'd be grateful.

[keyclone]

erp?!

ok, that's a first. i understand what you are saying... and it could be possible, but would require a new list mechanism... it's not a dnp list and its not the white list.. it's another list of keys for all but the active. (suggestions for name?)

i'll put it on the list.. hopefully, it'll make it into the next release

[Naysayer]

erp?!

ok, that's a first. i understand what you are saying... and it could be possible, but would require a new list mechanism... it's not a dnp list and its not the white list.. it's another list of keys for all but the active. (suggestions for name?)

i'll put it on the list.. hopefully, it'll make it into the next release

Lime green list!

j/k j/k
Something straight forward like "clone only" list might save you a few hours of explanations.

[keyclone]

Lime green list!

j/k j/k
Something straight forward like "clone only" list might save you a few hours of explanations.

maybe... but i like 'lime green list'

LG list?

[Abzalon]

erp?!

ok, that's a first. i understand what you are saying... and it could be possible, but would require a new list mechanism... it's not a dnp list and its not the white list.. it's another list of keys for all but the active. (suggestions for name?)

i'll put it on the list.. hopefully, it'll make it into the next release

Name suggestions: pass-to-background or pass-through-active

[Frosty]

Would there happen to be a way to pass keys to the clones, but block those keys from being executed on the Main PiP? Say I wanted to add a couple keys to turn my alts left and right, but I don't want this done on the main. I could just hotkey it through WoW interface on the alts, but when I switch through my clones with PiP I'd have a problem.

It would be kind of like black-list do not pass, but work for all background windows and exclude the main. If you have any solutions, I'd be grateful.

Just a thought, but would it be easier to just have a per account black list? Maybe tied to the startup command ID so it knows what window to send too?
I'm thinking that if it's useful for one situation, it might be useful to be able to pass keys to all windows but slave3, for example.

[Naysayer]

Would there happen to be a way to pass keys to the clones, but block those keys from being executed on the Main PiP? Say I wanted to add a couple keys to turn my alts left and right, but I don't want this done on the main. I could just hotkey it through WoW interface on the alts, but when I switch through my clones with PiP I'd have a problem.

It would be kind of like black-list do not pass, but work for all background windows and exclude the main. If you have any solutions, I'd be grateful.

Just a thought, but would it be easier to just have a per account black list? Maybe tied to the startup command ID so it knows what window to send too?
I'm thinking that if it's useful for one situation, it might be useful to be able to pass keys to all windows but slave3, for example.

Well, I don't have a set main character. I alternate through PiP so often that any of my characters could be in the main position at any given time.

When casting at a moving target, I use mouse turning to stay aimed in the right direction on my current main window. I don't like to have to drop my cast in order to turn my other guys, so if there were a "lime green list" I could continue my cast and turn my 4 clones at the same time to make sure everyone faces the target and blows the s**t out of them . Right now I'm using turn on all of my guys, and it forces my main to turn as well, so I have to turn him back with my mouse fast enough before the cast goes off, which can make you pretty dizzy and disoriented tbqb .

I hope i explained that clearly.

[Marlek]

I'm just a newbie, but I'd also like to see this functionality. I'm multi-instancing two feral druids, and it would be very nice to be able to control the positioning of the clone(s) independent of my main. Ideally I'd like to be able to control my clone with the arrow keys and control my main character with WSAD.

[Frosty]

Would there happen to be a way to pass keys to the clones, but block those keys from being executed on the Main PiP? Say I wanted to add a couple keys to turn my alts left and right, but I don't want this done on the main. I could just hotkey it through WoW interface on the alts, but when I switch through my clones with PiP I'd have a problem.

It would be kind of like black-list do not pass, but work for all background windows and exclude the main. If you have any solutions, I'd be grateful.

Just a thought, but would it be easier to just have a per account black list? Maybe tied to the startup command ID so it knows what window to send too?
I'm thinking that if it's useful for one situation, it might be useful to be able to pass keys to all windows but slave3, for example.

Well, I don't have a set main character. I alternate through PiP so often that any of my characters could be in the main position at any given time.

I gotcha now.