by rycher » Tue Feb 17, 2009 10:17 am
Ludek wrote:Yes, if you would like MM to force another app to stop retrieving the key/shortcut in case it is a MediaMonkey global key/shortcut then you need to use the PreferLLKeysHook = 1 to enable Low level Windows keyboard hook (used up to MM 3.0). Generally speaking it works fine, just it's a low level hack, for example some antivirus apps don't like it.
In MM 3.1 we use Raw input by default (WinAPI) and this is at a little higher and doesn't allow us to force another app to stop receiving the key/shortcut.
Ok, so there are still 2 cases:
1) Default configuration (i.e. without PreferLLKeysHook = 1): there is no delay before hotkeys stop being recognized by MM, but the foreground application can interpret the global hotkey (depends on the app).
2) Configuration with PreferLLKeysHook = 1: global hotkeys are never interpreted by the foreground app, but after ~3 seconds of holding part of the hotkey combination, hotkey stops being recognized by MM (keys must be released and pressed again for hotkey to work).
Before finding MM, I used Winamp (with the same hotkeys). I don't know how they did it, but the global hotkeys in Winamp never affected the foreground app AND there was no delay for them to work (I just checked with the same foreground apps I mentionned previously). It would be great if MM could behave the same way. I guess the question is: why does the low-level behaviour has this working delay, could it be increased/controled by another ini variable?
[quote="Ludek"]Yes, if you would like MM to force another app to stop retrieving the key/shortcut in case it is a MediaMonkey global key/shortcut then you need to use the PreferLLKeysHook = 1 to enable Low level Windows keyboard hook (used up to MM 3.0). Generally speaking it works fine, just it's a low level hack, for example some antivirus apps don't like it.
In MM 3.1 we use Raw input by default (WinAPI) and this is at a little higher and doesn't allow us to force another app to stop receiving the key/shortcut.[/quote]
Ok, so there are still 2 cases:
1) Default configuration (i.e. without PreferLLKeysHook = 1): there is no delay before hotkeys stop being recognized by MM, but the foreground application can interpret the global hotkey (depends on the app).
2) Configuration with PreferLLKeysHook = 1: global hotkeys are never interpreted by the foreground app, but after ~3 seconds of holding part of the hotkey combination, hotkey stops being recognized by MM (keys must be released and pressed again for hotkey to work).
Before finding MM, I used Winamp (with the same hotkeys). I don't know how they did it, but the global hotkeys in Winamp never affected the foreground app AND there was no delay for them to work (I just checked with the same foreground apps I mentionned previously). It would be great if MM could behave the same way. I guess the question is: why does the low-level behaviour has this working delay, could it be increased/controled by another ini variable?