script test() sayString("Trapped.") ... endScript And under your desired section in <APPBASE>.jkm: leftWindows=test On 11/13/2013 6:27 PM, David Pinto wrote: > Jim, > Thanks for your feedback, but despite attaching the windows key to a script, > that script is not invoked. Instead, the Windows key opens the start menu. > Note that in the Keyboard manager, the Add Keystroke dialog will not accept > a single windows keypress as a hotkey. But if I do a key combination with > the windows key, and then delete the second key, then I can successfully > assign the windows key to a script. I can also do this directly in the JKM > file by just typing it in. Nevertheless, the script is not triggered by the > Windows key. Perhaps you've done it a different way that works. If so, > please advise. > > One last thing. I was mistaken when I said the JAWS keyboard help mode did > not trap the windows key. It in fact does prevent the windows key from > passing through to the system. Maybe there's a hint of how to go about > things. > David > > ----- Original Message ----- > From: "Jim Bauer" <holdsworthfan@xxxxxx> > To: <jawsscripts@xxxxxxxxxxxxx> > Sent: Monday, November 11, 2013 2:41 PM > Subject: [jawsscripts] Re: Windows key > > >> Try binding a script to "leftWindows" in the app's JKM. (I don't >> presently have a right windows key here, but if one works, so too should >> the other.) >> >> On 11/13/2013 4:28 PM, David Pinto wrote: >>> Got a couple of related questions. >>> 1. Does anyone have a strategy to determine if the Windows key has been >>> pressed? >>> 2. Is there any way to intercept the Windows key from going to the >>> system? >>> >>> Basically, I've been frustrated in my ambition to take control of the >>> Windows key in scripted environments where students are getting in >>> trouble >>> by inadvertantly pressing the Windows key. Here's what I've noticed about >>> JAWS and the single Windows key. >>> 1. In JAWS keyboard help mode, the Windows key is not trapped, but rather >>> executes its function of opening the start menu. >>> 2. The Windows key doesn't register in the KeyPressedEvent () either in >>> the >>> currently loaded scripts or the default scripts that are invoked when the >>> start menu gains focus. >>> >>> So right now, the only way I know of determining if the Windows key has >>> been >>> pressed, is to test for its effect in the WindowActivatedEvent (). In >>> other >>> words, did the start menu open? Fortunately, before the currently >>> loaded >>> scripts unload and the Start Menu's default scripts load, the >>> WindowActivatedEvent () contains that information. At any rate, does >>> anyone >>> have a better strategy to determine if the Windows key has been pressed? >>> >>> Thanks in advance, >>> David Pinto >>> YesAccessible.com >>> >>> >>> __________ďż˝ >>> >>> View the list's information and change your settings at >>> http://www.freelists.org/list/jawsscripts >>> >> >> __________ďż˝ >> >> View the list's information and change your settings at >> http://www.freelists.org/list/jawsscripts >> > > __________ďż˝ > > View the list's information and change your settings at > http://www.freelists.org/list/jawsscripts > __________ďż˝ View the list's information and change your settings at http://www.freelists.org/list/jawsscripts