PiP Bug?

I dont know if this is a bug, unique to my setup, or just has to do with the way that Im using PiP.

But heres the anamoly:

I have my four WoW windows PiP set to the keybindings 1, 2, 3, 4. In WoW I am also using the keys 1, 2, 3, 4 to change focus. Its nice using 1 button to change screens and leader :)

I press 2 while on my main (PiP 1) and the screen moves.
Toons 2, 3, and 4 now have their focus set to toon 2.
Toon 1's number 2 button is half-pressed (stuck in the down position? I can see the white box around the WoW UI button) and hasnt changed focus but the screen moved.
I have to hit the focus twice (button number 2) in order for all toons to have the focus change.

A little further investigation showed me that everyone changes focus except for the last Main Screen. Is this a known problem? Is there a fix? Is it my setup? Is it unique with Vista 64?

Hope I explained that clear enough. let me know if you have more questions, it seems pretty consistent.

no one has reported it.. but i'll check it out.

(i've had this exact thing working for me for some time... but i'll look)

I have had the same problem, using the same kind of setup, also using keyclone, but I don't think it's a keyclone problem. Here is my original post:

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

The reason I don't think it's a keyclone problem is that I am not yet running my 5 man team on that powerful a computer, and I think it is something to do with that rather than anything else.

If my Q6600 overclocked at 2.7Ghz and 8Gb of Ram isnt high end enough...I guess this is an excuse to upgrade to an Extreme Quad Core...It must be that im lacking 12MB of cache.

Get back to me, Ill quote the post and use it to convince the wife :P

I recently upgraded my Keyclone, and used to have it setup to switch my main screen from char 1, 2 and 3. I used Ins/Home/Page Up. Now, it doesn't work, and I cannot type anything into the PIP in my maximizer screen.

What am I doing wrong?

@hotdogsrgross
a bit confused by the description. worst case scenario... close keyclone, delete your settings (keyclone.ini file) and reconfigure.

also, please make sure you are using v1.8k (and not the alpha or beta of v1.8k)