The lower timings (event wait/foreground wait) the more chance the camera is gonna go whacko or miss a click.

In the case of the foreground window missing the click before it switches to and back from instance 2... try increase Event Wait.

Foreground wait is just an additional delay one can add to the mix if click down's are being missed...

But generally event wait is for any click or movement... to give time for WoW to process it before getting confused....

Cameras going whacky, my best guess, is its moving to the next window too fast for WoW with the default values, so it receives a relative movement whilst WoW *thinks* the mouse is down. Of course even with 0 ms event wait Octopus will have said release the click prior to moving, but I expect Blizzard dev's were not too concerned about making it respond to clicks for a <100 ms session.. who knows what they are doing, probably processing movement before clicks. One can only speculate. But since they can't even write follow code, do you expect them to write it for <100 ms clicks turbo alt tab style???

The original post didn't even mention the timings, I should probably write in bold text WoW only accepts clicks in the foreground. Alt tabbing is not random, its necessary, its the timings that are critical.

if you increase the timings to 500ms say, you'll see the problem is probably not with my code, but how WoW responds under pressure :P