Thanks for keyclone, and a problem I have.

[gbremset]

So.. Firstly, let me thank keyclone for your awesome tool... Life as a multiboxer has become a dream now.

However, I appear to be having a problem occationally, and I'd like to hear if you know what's causing it.
I've tried looking through the threads here, but haven't found anything helpful (If there is a thread, just link it and I'll read there)

Some times when trying to control one of my slaves, such as turning in quests, picking up loot etc, the mouse just jumps out of that window, and that character becomes uncontrollable until I find the right "trick" to click it back into action. Some times they start running, but most of the time they just stand there. Then, when I try to put my mouse in that window, it gets instantly thrown out and sent back to the window I came in from.

It appears as if the last pressed mouse button gets stuck, and from when I try to replicate the issue, it seems I can solve it by first getting my mouse stuck in the window by holding a mouse button down, then quickly double clicking the button in question. If I'm too slow at double clicking the button, I have to try again.

I have the latest version of keyclone.

[Diamndzngunz]

Same thing happens to me, my mouse jumps randomly sometimes, back to other wow window after I click out of it, not sure what causes it, but its retarded.

[keyclone]

G'morning guys,

yes, that bug (retard-o-mouse) is a bit persistent. basically, when you click-drag on a wow window, blizzard will move its cursor outside and to the left of the window you are working with. it's generally hidden and the focus won't jump to another window... if blizzard is holding the mouse. but, once in a while (i love that part).. blizzard will release the mouse on mouse-up and the cursor will be over the other window.. yet the mouse-up event has not yet been received by the first blizzard window. and if the other window is one of your keyclone'd windows, then keyclone will push focus to it... without pushing the mouse-up event to the first window. this leaves the blizzard window thinking the cursor is supposed to be outside and to the left of itself...

this is a race condition and does not happen all the time. i have been trying to find a work around, hopefully it'll be resolved in the next release.

and yes, the user fix i have found was quick clicking into the bugged window.

of course, you could turn off focus-follows-mouse.. but i personally really find it useful and put up with the bug when it happens (and curse the stupid dev every time )

sorry about the hassle.

Rob

[gbremset]

Hi Rob.

This is absolutely no hassle at all.. For such a great program as keyclone is, that little bug is worth struggling through..
However.. If I deselect Focus Follows Mouse (I'm not at home righjt now, so I can't try it) does that mean that I have to click into the window, before I can select anything inside that window? And that removes the issue completely? Because if so, I may switch to that until you've got a fix.

Anyways.. I used to work with programming control systems (CUE - www.cue.cz), and their touch panels, and would get a similar issue if customers had more than one contact on the touchscreen at once (ie. Holding your touchpanel so your thumb touches the screen along the edge, and then pressing a button), and that would confuse the panel and make many buttons press at the same time.
What I did to solve that, was to constrict the edge of each button, so that the last button pressed, restricted functionality in the rest of the touch panel until that button was released.
Maybe something similar could work for keyclone? When keyclone has a mouse button down, it uses the information from maximizer to restrict mouse movement to that window only, or something like that? That's my 5 cents anyway.. Mind you.. Programming the control system was done in a VB clone, and all the functionality for touch panel restriction was built in to the system, I don't expect it to be a piece of cake in your world. :P