thanks! I really haven’t found any great solution, but I need something that works for the little I do with windows these days. I am currently using version 8 of window eyes, but am switching to nvda since I think it’s now a wonderful peice of software.
thanks for both the directions sets for this fusion way and the one with seal. Cait > On Mar 26, 2015, at 3:39 PM, Grant Hardy <[email protected]> wrote: > > Caitlin, > > Here are the steps for the Fusion-only way, based on instructions I’ve > written previously to the list. It’s been a while since I’ve used this > method, but I think these instructions still apply. > > Press CMD+COMMA to open preferences from within VMWare, and select the > “keyboard and mouse” section. Be sure you are editing the right profile, then > choose the “key mappings” tab and hit the add button. > > Once you enter the dialog to add a new key mapping, you can do a couple of > things. It’s best to navigate the dialog with VO+LEFT and VO+RIGHT rather > than the TAB KEY, otherwise VMWare could interpret the TAB KEY as the key you > want to remap. > > The two controls which VoiceOver calls combo boxes can actually be typed into > as well. So, as an example, let’s say you want to remap the GRAVE ACCENT KEY > to act as an INSERT KEY. That’s far from ideal, of course, but since it is > just one key above the caps lock key, which is normally the screen reading > key, this is an okay compromise if you don’t want to use other third-party > software. in the first combo box that asks what key you want to remap, if > you just push the GRAVE ACCENT on the keyboard, it should take. In the second > combo box, use VO+SPACE to expand the list, find INSERT by using VO+LEFT and > RIGHT, move the mouse pointer there with VO+COMMAND+F5, then perform a click > with VO+SHIFT+SPACE. That’s it, your choice should be saved. Stop interacting > once, find the OK button and activate it, and you should be done. Ensure the > “enable key mappings” checkbox is checked as well on that page, then close > out of preferences with CMD+W. > > If this is still not working for you, start up the virtual machine where > you’re having problems and hit CMD+E to open the preferences window for the > virtual machine. Activate the keyboard and mouse button, and make sure the > same profile you just edited in the previous step is selected. > > The insert key is generally not treated exactly the same way as the caps lock > key by Windows screen readers, leading to possibly undesirable key mappings. > You might be able to install SharpKeys and remap insert to caps lock, but > I’ve not had success trying this. > > I hope this helps. > > Grant > > On Mar 26, 2015, at 5:41 AM, Caitlyn Furness <[email protected] > <mailto:[email protected]>> wrote: > > I’d like the steps in remapping the insert key within fusion using just the > fusion way, please. > > I thought I had done this, but it doesn’t seem to be sticking. > > thanks, > Caitlyn > >> On Mar 25, 2015, at 10:33 PM, Phil Halton <[email protected] >> <mailto:[email protected]>> wrote: >> >> possibly the easiest way around the caps lock problem is to set nvda, or >> JAWS, to use the insert key as its modifier. Then in fusion key remapping >> preferences, you can set a key like the grave accent to instead produce an >> insert key. Then, essentially, the grave accent key which is just above the >> tab key will serve as the nvda modifier key. >> This method does not require the use of any other software like sharpkeys >> and the like. >> Personally, I use sharpkeys to set the grave accent key to act as the caps >> lock and have JAWS set to use the caps lock as modifier. However, I have >> used the fusion insert key method as well with equally good, if simpler, >> results. >> Remapping the insert key in fusion settings is a bit tricky, but can be done >> without too much trouble. If you go that route, I or someone else can walk >> you through the process. >> >>> On Mar 25, 2015, at 4:30 PM, Andrew Lamanche <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi Bill again, >>> >>> I've found the post from Grant - one of the list members - outlining the >>> steps you need to take to use capslock key successfully in fusion on a mac >>> computer. I assume you use a mac computer although having read your >>> message again, I see you say "windows" keyboard. So I'm not sure whether >>> gRant's message is going to relevant. I'm pasting his message in quotes >>> below. Maybe you could contact him via the list if what he says will not >>> work or you need further help. I know it's a headache. Look for the quoted >>> message below my signature. >>> >>> Andrew >>> "Hello all, >>> >>> I am very happy to report that I have found a solution to give Windows >>> complete control of the CAPS LOCK KEY while using it in a VMWare virtual >>> machine. I now have full use of my CAPS LOCK KEY while using Windows in >>> VMWare. For example, with JAWS, I can use it as my JAWS KEY, and I can >>> press it twice quickly to toggle CAPS LOCK on or off. While I was willing >>> to settle for using another key like the GRAVE ACCENT KEY as my screen >>> reading key, or even to map my CAPS LOCK KEY to an INSERT KEY, I wanted to >>> see if I could find a solution that would allow the CAPS LOCK KEY truly to >>> be passed through to Windows. The reason is primarily because screen >>> readers don't always treat the CAPS LOCK KEY identically to how the INSERT >>> KEY is treated, even while using a dedicated laptop layout. In JAWS, for >>> example, there are many key mappings which are different, such as INSERT+8 >>> (open the keyboard manager) as opposed to CAPS LOCK+8 (perform a left mouse >>> click). While JAWS key mappings can be changed, and while I love using >>> VMWare Fusion and find it very efficient, I really wanted my keyboard to >>> work in a more familiar manner. >>> >>> If anybody is wondering whether the CAPS LOCK KEY can be passed through >>> directly, the answer is yes, and here is my solution. The short version is >>> that in Mac OS X, we’ll be mapping the CAPS LOCK KEY to something entirely >>> different. Then in the VM, we’ll install SharpKeys and map that different >>> key back to CAPS LOCK. While this sounds a little crude, it’s the best >>> solution I’ve come up with thus far and really isn’t too complicated to set >>> up if you know your way around Mac OS X. The irony is that while you have >>> this configured, you won’t be able to use CAPS LOCK within Mac OS X itself. >>> It will only work when working with your virtual machine. You can select >>> text then choose “Make upper case” or “Make lower case” to compensate for >>> this. These options are located in the menu bar under Edit > >>> Transformations. >>> >>> 1. Open up System Preferences. Select the Keyboard button, then the >>> Modifier keys button. Change CAPS LOCK to “no action” then hit OK and exit >>> out of System Preferences. >>> >>> 2. Download and install Seil from https://pqrs.org/osx/karabiner/seil.html >>> <https://pqrs.org/osx/karabiner/seil.html>. It is a small app that lets you >>> customize the functionality of the CAPS LOCK KEY as well as some other, >>> international, keys. I believe this software is reputable, but I definitely >>> understand and share the hesitation that many will feel about installing an >>> app from outside the App Store that you may never have heard of. >>> >>> 3. Once installed, open the Seil app from your applications folder. You can >>> navigate through this app by tabbing around. Find the tree of settings. At >>> the top you will see text that says, “expand tree, then change settings and >>> change key codes”. Arrow down and the first group within the tree view >>> should be “change the CAPS LOCK KEY”. Expand with a RIGHT ARROW then DOWN >>> ARROW to the first and only setting you need to change, “change the CAPS >>> LOCK KEY”. Reassign the caps lock key to something else. I assigned it to >>> key code 110. This is the "super key" in Linux or the "applications key" in >>> Windows. Since my Mac doesn’t have this key anyway, this shouldn’t cause >>> any other key conflicts and I think should be a safe bet. Tab to the >>> checkbox that indicates you want this setting to be applied and check it, >>> then TAB to the edit box and enter the appropriate keycode, 110 in my case. >>> You can now close the window with CMD+W. >>> >>> 4. Now, whenever you press the CAPS LOCK key in Windows it will open up a >>> context menu. This is not what we want, so go ahead and install SharpKeys >>> to your virtual machine from https://sharpkeys.codeplex.com >>> <https://sharpkeys.codeplex.com/>. It is very easy to navigate. Open it up. >>> Reassign "special@_Applications Key" to caps lock, and hit the write to >>> registry button. Then reboot the VM or log out and back in. Voila, you now >>> have full use of the CAPS LOCK KEY within Windows. >>> >>> 5. You should easily be able to undo this change in Seil if desired. >>> >>> Sorry that this was so long winded but I wanted to provide a reasonable >>> amount of detail for those interested. It may well be that somebody else >>> has a much more brilliant solution than mine. >>> >>> Cheers. >>> >>> Grant >>> >>> >>> >>> Grant" >>> >>> >>>> On 25 Mar 2015, at 16:00, Bill Holton <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> Hi. >>>> Running Windows 7 in Fusion with a Windows keyboard, I cannot seem to use >>>> the caps lock key as an NVDA modifier. I have the setting enabled. Does >>>> NVDA not see the caps lock key in a Fusion Window? Thanks. >>>> Bill >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "MacVisionaries" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to [email protected] >>>> <mailto:[email protected]>. >>>> To post to this group, send email to [email protected] >>>> <mailto:[email protected]>. >>>> Visit this group at http://groups.google.com/group/macvisionaries >>>> <http://groups.google.com/group/macvisionaries>. >>>> For more options, visit https://groups.google.com/d/optout >>>> <https://groups.google.com/d/optout>. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "MacVisionaries" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected] >>> <mailto:[email protected]>. >>> To post to this group, send email to [email protected] >>> <mailto:[email protected]>. >>> Visit this group at http://groups.google.com/group/macvisionaries >>> <http://groups.google.com/group/macvisionaries>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MacVisionaries" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] >> <mailto:[email protected]>. >> To post to this group, send email to [email protected] >> <mailto:[email protected]>. >> Visit this group at http://groups.google.com/group/macvisionaries >> <http://groups.google.com/group/macvisionaries>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/macvisionaries > <http://groups.google.com/group/macvisionaries>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/macvisionaries > <http://groups.google.com/group/macvisionaries>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout.
