Quote Originally Posted by 'skarlot',index.php?page=Thread&postID=76477#post7 6477
i used Setpoint to set buttons (4-5 and other ones - not l/r/m) to letter keys with no problem.
Yup. Left the left, right, middle click and scroll alone. Set the "extra" buttons to keystrokes.

Quote Originally Posted by 'skarlot',index.php?page=Thread&postID=76477#post7 6477
I recognized a problem in my code with the internal mouse->key mappings which used scan codes, which *I think* differ between countries/keyboard layouts, and I meant them to use virtual keys like key->key mappings. I gotta adjust this, but it's unrelated.
Whoosh! I hope you were just thinking "out loud"......

Quote Originally Posted by 'skarlot',index.php?page=Thread&postID=76477#post7 6477
I don't get it, because all I am doing is taking the information, and passing it back again via SendInput, which shouldn't be any problem locally or on a client... the only thing I can possibly do is take the keyboard hook and allow it to pass when local, which I would think achieves the same thing. Is that right, it's stopping keys locally from Setpoint?
If I understand that right, then yes, for some reason Octopus isn't "getting" the keys.

One thing I forgot to add: When in Server->Keys I could enter keystrokes/combos with my keyboard and G-11 macro keys, but the mouse keystrokes got no response.

I'm at work now but once I'm home I'll try setting the mouse on program-specific with the program set to Octopus and see if that does anything.

UPDATE: got home from work and tried it out on a different computer, this one running Win XP, SP3. On this system Octopus recognizes the mouse "keystrokes". So it sounds like it has something to do with the vista drivers for the mouse or something like that.