'Headless' macro not quite working how I would like, any thoughts?

I have finally made some macros for my shaman, mainly copying/borrowing from Ken's complete shaman macro set: http://www.dual-boxing.com/wiki/inde...aman_macro_set

My setup is 1 computer, keyclone, 1 monitor, maximizer set for one large viewing area for my main and 4 smaller areas down one side of the screen for my slaves.

My idea is this: Set keyclone PIP hotkeys as the same as I have set for the hotleys for my focus macro in the game, i.e. I hit Shift-F2 to switch to my first slave and it also runs a macro in game which changes focus for all chars to use that char as the focus. Here is the macro:

/clearfocus
/focus [target=Shammy2, exists, nodead]
/follow focus

I admit that I am still very new to macros and so forth, so it isn't the most elegant, but it does 'work', however there is one small problem...

I have 5 of these macros for each character, and each one is hotkeyed the same, so that Shift-F2 will always trigger the same macro on all shammies. It works as I would like it to for all the shammies, APART from the one that was the last focus. i.e. If I change from Shammy3 to Shammy 4, all shammies APART from Shammy 3 get the new focus and follow the new leader. If I hit the same macro again, then Shammy3 seems to wake up and do as he should. What may I be doing wrong and is it something really obvious, or does this just not work like this? As far as I can tell the old leader char isn't clearing focus, or isn't getting the new focus.

Edit: Just to be clearer, it's always the old leader that doesn't change focus.


Thanks in advance, hope this isn't too noobish :)

Here's a suggestion: change your macro so instead of "/follow focus" on the last line, do "/target focus" and verify after pressing the key that the previous leader targets the new focus. If not, it's the focus command that's failing. If it does, then it's just the follow command that's failing. Depending on where the problem is, you can work around it in a variety of ways.

Thanks for the reply, I did some testing after the PIP changing by getting all chars to type /p f %f t %t to tell me what they are focussing on and what they are targetting. All of the focuses are on the new focus, apart from the old leader that still has himself as the focus. I don't know what else to add apart from that, but I would be interested to know the workarounds, the only one I know that does work is pressing the PIP focus key again which seems to solve this. I don't think it's a keyclone problem, it may just be that my computer can't keep up with the PIP changing and passing the command to the now lower priority window, but if I have to live with 2 key presses then so be it :)

Edit: Instead of a wall of text, the short answer: definitely focus change failing.

I've seen this issue as well. The problem appears to be that wow ignores keyboard input while its window is resizing.

I use a similar setup but do not have this problem at all... the only difference perhaps is in that I use only one macro per instance to change focus / group leader and change PIP.

as shown here http://www.dual-boxing.com/wiki/inde...with_modifiers

the only time I have any issues is when focus is on a small window then I get unexpected PIP swaps ;)

Thanks for the replies, I have gotten used to pressing the key a few times now on PIP swaps, it's not that often, was just curious about it, but I kind of reached the conclusion that it may be some lag within WoW due to the window changing. Djarid, I did see your macro and was gonna use it but as I was starting out I thought it best to avoid too many modifiers for now, I am sure this will change as I progress anyway, but be assured that I did see your macro and many others in the http://www.dual-boxing.com/wiki :P

Quote:

---

Originally Posted by 'Djarid',index.php?page=Thread&postID=84037#post84 037

I use a similar setup but do not have this problem at all... the only difference perhaps is in that I use only one macro per instance to change focus / group leader and change PIP.

---

Its more likely that your machine performs the pip switch fast enough to still be able to process the key press in wow.