If you edited the one KCHR resource, it will be selected automatically if you made a copy, you'll have to select it." You should have your customized keyboard available from the Keyboards system preferences panel. Rename the modified copy of Localized.rsrc (probably named Localized.rsrc copy) so it is just plain Localized.rsrc, and be sure it's in the right folder (it will be, unless you moved it out).ħ. Rename your copy of Localized.rsrc to Localized.old (safety)Ħ. Run QuickConvert again and switch the resource fork back to the data fork.ĥ. This way you can go back to the original keyboard mappings any time you want.Ĥ. Alternatively, create another KCHR resrouce, give it a different name (like "Modified US") and edit that resource. Now run ResEdit and edit the KCHR resource in your copy of Localized.rsrc. Use AutoHotkey script 'OS X keyboard for Windows' to remap basic shortcuts (see 'OS X keyboard for Windows' AutoHotkey script).
#Windows keyboard mapping for osx mac os
But, again, don't worry, in the end shortcuts physically will be the same os on Mac OS X. Note there's another program out there called QuickConvert which does Mac file and creator type modification it's a fine program but not what you want.ģ. So we stick to more traditional 'Control'-shortcuts on the OS level. This is just the computers way of identifying the. You may be greeted with a Keyboard Setup Assistant prompt like the one in the image below.
You should be able to use it as soon as its connected. So get a copy of QuickConvert and switch the data fork to a resource fork. To use a Windows keyboard, simply connect it to your Mac (if its a Bluetooth keyboard, your Mac should recognize it when you turn on the keyboard). The keyboard mapping information is stored in a KCHR resource in that file - but the file has the resources in the data fork. (f you're using more than English, you may have to do this for each language I haven't tried other languages). System/Library/Frameworks/amework/Frameworks/amework/ Resources/English.lproj/Localized.rsrc. A little tedious, but it seems to work like a charm. For a long time my inability to do this (I learned to type on a Selectric keyboard, and hate it when shift-period produces > instead of a period) was one thing that kept me from going to OS X full time.
#Windows keyboard mapping for osx how to
"I see that someone asked how to modify OS X keyboard mappings.
I have read the aricle on, but they are poiniting out a rather unsupported utility called QuickConvert. I did the trick under 9.x, but I have no luck under OSX. I need to swap Alt & Windows button function, because now Windows button is acting like Command, and I really would like to use Alt (it's obvious) as Command. I'm using a standard Windows USB keyboard.
0 kommentar(er)
