--- In [email protected], sgp <[EMAIL PROTECTED]> wrote: > > Deen Hameed wrote: > > > The normal trigger for a hotkey is = > > What do you mean by "trigger"? > PowerPro hotkeys don't have triggers. PowerPro macros do. > Are you having a problem with macros or hotkeys? > If macros, have you tried changing your macro trigger key, and see if that helps? > Are you accessing your PC directly or through a remote control program of any kind? > Is your keyboard a US keyboard or a different locale? > Sorry, I've been rather slack with the terminology.
I don't actually have a problem with the macros; not that I'm aware of anyway. What actually happens is that some keys (say b f t l etc) start getting 'trapped' somewhere and the keyboard will not respond to those keys anymore. If I wait a long time, those keys will eventually turn up and be printed up on the screen (out of sequence, of course). Killing powerpro will usually fix that problem. I'm quite sure it's not my macro key. Turning off the HotKeys, I never get the missing keystroke problem, although I could probably wait longer before jumping to that conclusion. I've checked my hotkeys list for duplicates, and cleaned up any unused keys. The only other thing that has substantially changed, and which is waiting for a trigger from the keyboard is the CodeAccelerator script (which I activate using the RightSquareBracket key) FYI, I'm accessing the machine locally, although there is also another machine that I access through Synergy. The keyboard locale is English (Australia) - US. The problem occurs whether the machine is local or through Synergy (the solution works in either case, too). I might just try changing the HotKey for CodeAccelerator (or turning it off entirely) and see if perhaps that's where the problem arises... Would piss me off big time though as I seriously adore that script. Best Regards, Deen 19/05/2008 20:32:06
