Jump to content

Search the Community: Showing results for tags 'shortcut'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 3 results

  1. After installing my iAtkos v7 on my Intel Chipset i found a very Critical issue,Specially for the Previously Windows users that is Shortcuts are now working Correctly So after a frustration i Wrote this post that might solve your issues This post explains the steps I took to make my PC keyboard work more like a Mac keyboard. The goal here is not necessarily for keys with the same names to be in the same position (e.g., the Ctrl key), but rather to have the same functionality across platforms when pressing keys located in the same positions. When I started using OS X, I quickly realized that it uses a different set of key bindings. For example, the key binding for copying is Command-C, and the Command key on a Mac keyboard is located in a different position than the Ctrl key is on a PC keyboard. I decided right away to modify the Mac key bindings so they would be more like the bindings that I was familiar with. If I was committed to completely switching platforms, I would have given more consideration to learning a new set of key bindings. However, since I was still planning on using multiple platforms, I wanted to make switching back and forth as seamless as possible. Here are the steps for configuring the Mac’s keyboard to work like a PC keyboard. Step 1. Configure Modifier Keys The first step is changing the Modifier Keys… settings in the keyboard settings in system preferences. The settings are shown below. Click Apple icon on Menu Bar >> System Preferences . . . >>Keyboard & Mouse >>Modifier Keys After that Configure the settings as in the picture. . .same to same... Step 2. Create DefaultKeyBinding.dict The next step is to create a DefaultKeyBinding.dict file to add additional settings that make the bindings more similar to a PC (e.g., Ctrl-Left to move the cursor one word left, which will now be Command-Left on the Mac since the Command key is now—after Step 1—located where Ctrl is on a PC keyboard). I used KeyBindingsEditor to create the following DefaultKeyBinding.dict file: DefaultKeyBinding.dict DefaultKeyBinding.dict.zip The file should be saved to ~/Library/KeyBindings/, where ~ denotes your home directory. If you can’t see the Library directory in Finder, then click Go –> Go to Folder…, and enter ~/Library. Here Generally You Would not find the KeyBindings folder So go ahead and create it and place the DefaultKeyBinding.dict DefaultKeyBinding.dict.zip file in it . . .Thats it Done!! Restart and Works
  2. Hi all I've been trying to solve a problem. I'm trying to write an Applescript that does the following, I have spent numerous hours trying to get it work but still not going anywhere near. The algorithm is actually simple, as below: if (window whose title contains text "[my google email address]") does not exist then create a new Chrome window with address "https://mail.google.com/mail/u/0" put the window in presentation mode else if (window whose title contains text "[my google email address]") exists but does not have focus, or hidden then bring focus to the window else hide the window end if end if Could any one help to suggest what code would work? Thanks heaps MacBook Air, OS X Mavericks (10.9.1)
  3. Many People gets confuse due to their wrong keyboard hotkeys or completely disabled hotkeys while using VoodooPS2Controller.kext. today I am writing a little guide for newbies to Enable Possible Every disabled Hotkeys on laptop with their personalised shortcuts. Common Issues Can be Solved Using this guide: Media Hotkeys not working Brightness Hotkeys not working Wrong keyboard entries Completely dead keys Bringing Every Windows hotkeys to Mac Basics: While our laptop keyboards use PS2 Methods for input in windows, Mac Uses ADB Codes for Its Keyboard.VoodooPS2Controller convert those PS2 codes to Mac compatible ADB Codes. All the PS2 Scan codes for universal keys like ( A-z, 1-0, !-+) are same for almost every laptops but OEM Hotkeys are different. All laptop has Different Functional keys.So hot keys usually don't work properly without proper edits. To Solve this issue First find the codes for your system then remap them to specific Mac ADB codes to do the same exact output in system. (Note : I learned about all these things from different people and different posts, I will try to link Original Posts.) !!Huge Thanks to RehabMan & All VoodooPS2Controller tester and developer!! 1.Check your Functional keys First of all you need to check wether your functional keys transmits PS2 or EC scan codes. Install latest version VoodooPS2 kext debug version, and watch your console while pressing keys. A. PS2 Scan Codes If It is a PS2 Scancode then you will get some report as like this. (moniter Using ApplePS2 in search box and "NOW" option activated.) ApplePS2.. : Sending e022=69 down ApplePS2.. : Sending e022=69 up The first value is your PS2 Scan codes and the value after equal to is the ADB code injected to system. If nothing happens then it might be a EC Query. VooDooPS2 Github Link B. EC Queries Install ACPI Debug kext: https://github.com/R...OS-X-ACPI-Debug Open MaciASL and click on patch.(Add rehab man repo) Apply "Add DSDT Debug Methods" and "Instrument EC Queries" Patch Save the DSDT and restart Now go to console and search for "ACPIDebug" and press those keys ACPI Debug Github Link You will get some result like this ACPIDebug : EC _Q12 2.Get your new Keys A.Direct ADB Some hotkeys like play/pause, scan next track,Brightness,Lunchpad are exist in real Mac so you can find there ADB codes directly. You can remap your hotkeys directly to those ADB Codes. Some ADB Codes Play/Pause : 34 Next Track : 42 Prev.Track : 4d Others ADB codes can be found in this page. You can check those ADB Codes you can easily. Convert the ADB codes to Decimal from hexadecial. While VOODooPS2 Debug version is installed,Hold the right alt and press the decimal value then leave the alt key and you can see the Executed ADB code.( For e.g. ADB code for next track is 34 so in decimal it will be 66. So press alt then type 66 and release the alt.your track will be changed in your music player) B. Extra Function Key Some Hot keys like Lock windows,Print Screen,HP/Dell Support key, print, Multi monster setup are not present in Mac. In that Case you need to Assign those hotkeys to function keys like (f15, f16,f17...f20). After that in Mac Keyboard shortcut preference you can set them for various commands (Note: take help of Automator to create more personalised shortcuts) ADB Codes for function Keys f16=6a f17=40 f18=4f f19=50 f20=5a 3.Remap Keys A. PS2 Codes Go to your latest VoodooPS2 kext. Detailed specification on Github Page. Open " VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Keyboard.kext/Contents/info.plist" with Xcode or Plist Editor. Go to Custom PS2 to ADB Map Section Information Property List >> IOKitPersonalities >> ApplePS2Keyboard >> Platform Profile >> Default >> Custom ADB Map enter your PS2 Scancodes = ADB Value you want to use( In Hex) <key>Custom ADB Map</key> <array> <string>e022=34</string> <string>e024=4f</string> </array> B. EC Contolled Keys With Proper DSDT Edit you can Notify to PS2M for any EC Controlled Queries. Example for Brightness Fix (Original Post) into method label _Q11 replace_content begin // Brightness Down\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0205)\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0285)\n end; into method label _Q12 replace_content begin // Brightness Up\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0206)\n Notify(\_SB.PCI0.LPCB.PS2M, 0x0286)\n end; Custom EC Queries Shortcuts can be done by similar process.(Will Be updated Soon)