Hi David, sorry, but when I changed my dropbox hotkey to the same value you use, pressing it twice quickly still worked. Could this be an issue with the keyboard you are using? for instance, if you lift your fingers up from the keys, letting them all come back up, before the second press, will it work then? If so, maybe that's the keyboard, and the way it operates with use of the shift key perhaps (I don't know, am just guessing). anyway, it worked ok with me and 7.5.1; I think you're using 7.2? maybe it's an issue with 7.2 then? Chip
_____ From: David [mailto:[email protected]] Sent: Thursday, August 04, 2011 1:37 PM To: [email protected] Subject: Double-hotkeys and the script manager Well, I have realized this strange thing with one app so far. Just wonder if that is a fault in the app itself, or if this is reproduceable with other apps as well. The app I experienced it with, was the Dropbox app. The app is shipped with the hotkey of Ctrl-Insert-D. You press the hotkey once, and one behavior is performed. You press the hotkey twice rapidly in sequence - double-pressing the hotkey - and another task is performed. This works pretty well. Now, my problem is, that I wanted to switch to another hotkey. I opened 'script manager' (still on WE7.2). Then got to the hotkey manager, and entered my new hotkey, Shift-Insert-X. So far, everything went well. When I closed the hotkey - and script manager, and wanted to test my new hotkey, the problem arose. I can press the new hotkey once, and the first task is carried out perfectly. But when double-pressing the hotkey, nothing like the second task is performed. Somehow, it seems to me, that the hotkey manager did change the first press of the hotkey, but does not care to handle cases where the hotkey is set up for double-actions. Is this the case? And, since I am planning to use the same kind of double-acting hotkeys in one of my apps, is there a way for me to ensure that the user will be able to change his hotkey, and still have the double-action thereof? Or, could it be we here have run into a bug of Window-Eyes?
