Sorry in advance for multiple topics in the same message.
I used DC on 10.4 without any problems. I just installed it on 10.5.6 and set up everything, but nothing's happening. No crash log file, nothing. No keybinding created in ~/Library/Key Bindings, where I suppose the file should be (am I wrong?).
I use KeyFixer for now and I'm ok with it, but for some apps, it doesn't do the trick (Firefox or the Terminal for instance). In fact I'm not sure if DC would have the same limitations regarding particular applications, I don't remember testing those specific apps on my previous 10.4 system.
If it would have the same limitation, then how about trying to remap the keys with other keystrokes, like it's possible to do with Autohotkey on a PC? For instance, home key would "through back" command-left and end key, command-right...
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, first, DoubleCommand has nothing to do with Key Bindings, so nothing will be created in that folder.
It works inside the kernel, so it applies to all applications in exactly the same way - in fact it can't tell what application is going to end up receiving the keystrokes.
I think that answers everything you asked?
-Michael.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The keybinding was a thing I was mistaken about, but my problem remains: Doublecommand doesn't work on my machine. The interface does, but the functionality, not. Whatever I check or uncheck, save or apply, doesn't make any difference at all.
My other question was about remapping keys to make them simulate other keys; i'd be curious to know if there's a way to do that as easily as it is on a pc with autohotkey (autohotkey.com).
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sure a search would show up any on-the-fly-key-re-mapping software for the Mac, but as for DoubleCommand not working, it's a little hard to diagnose with only that information.
What does running the below in Terminal show you?
kextstat | grep DoubleCommand
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry in advance for multiple topics in the same message.
I used DC on 10.4 without any problems. I just installed it on 10.5.6 and set up everything, but nothing's happening. No crash log file, nothing. No keybinding created in ~/Library/Key Bindings, where I suppose the file should be (am I wrong?).
I use KeyFixer for now and I'm ok with it, but for some apps, it doesn't do the trick (Firefox or the Terminal for instance). In fact I'm not sure if DC would have the same limitations regarding particular applications, I don't remember testing those specific apps on my previous 10.4 system.
If it would have the same limitation, then how about trying to remap the keys with other keystrokes, like it's possible to do with Autohotkey on a PC? For instance, home key would "through back" command-left and end key, command-right...
Thanks
Ok, first, DoubleCommand has nothing to do with Key Bindings, so nothing will be created in that folder.
It works inside the kernel, so it applies to all applications in exactly the same way - in fact it can't tell what application is going to end up receiving the keystrokes.
I think that answers everything you asked?
-Michael.
Thanks for the reply Michael.
>I think that answers everything you asked?
Sorry to disappoint, but no ;)
The keybinding was a thing I was mistaken about, but my problem remains: Doublecommand doesn't work on my machine. The interface does, but the functionality, not. Whatever I check or uncheck, save or apply, doesn't make any difference at all.
My other question was about remapping keys to make them simulate other keys; i'd be curious to know if there's a way to do that as easily as it is on a pc with autohotkey (autohotkey.com).
Thanks
I'm sure a search would show up any on-the-fly-key-re-mapping software for the Mac, but as for DoubleCommand not working, it's a little hard to diagnose with only that information.
What does running the below in Terminal show you?
kextstat | grep DoubleCommand