Physically removing the Windows key is not an option for me. Instead, I need to be able to selectively trap or pass the Windows key through to the system. Right now, I am interested why JAWS ability to invoke a script that I've assigned to the Windows key should be disabled when the JCF setting distinguishing between the extended and numpad keys is enabled. I keep this option enabled in order to help students distinguish paired keys. Turn that JCF option off, and presto bingo! The Windows key is bound to the script I created for it. Go figure. Anyone have a clue? David ----- Original Message ----- From: "Travis Roth" <travis@xxxxxxxxxxxxxx> To: <jawsscripts@xxxxxxxxxxxxx> Sent: Tuesday, November 12, 2013 6:03 AM Subject: [jawsscripts] Re: Windows key trapping partly resolved > If you really want to disable the Windows key then using SharpKeys would > be > a more fail safe solution and would not require the use of JAWS. > Sharpkeys does some Windows registry hacks so it is not screen reader > dependent. > -----Original Message----- > From: jawsscripts-bounce@xxxxxxxxxxxxx > [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of David Pinto > Sent: Wednesday, November 13, 2013 8:24 PM > To: jawsscripts@xxxxxxxxxxxxx > Subject: [jawsscripts] Re: Windows key trapping partly resolved > > Jim, > I found out why I couldn't trap the Windows key as you proposed. In the > JCF > file of MyApp, I had the setting UseExtendedKeys=1, because I need to > differentiate between the numpad keys and the extended key equivalents, > like > 6 pack Home versus NumPadHome. And This is what's weird. When I set > UseExtendedKeys=0 in the KCF file, then the Windows key that is assigned > to > a script, indeed traps the windows key. But if I have UseExtendedKeys=1, > then the Windows key that is assigned to a script does not invoke the > script. Any ideas? > David > > ----- Original Message ----- > From: "Jim Bauer" <holdsworthfan@xxxxxx> > To: <jawsscripts@xxxxxxxxxxxxx> > Sent: Monday, November 11, 2013 4:59 PM > Subject: [jawsscripts] Re: Windows key > > >> 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 >> > > __________ďż˝ > > 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