Normal
This is the way MP handles these things. On first call it's a bit slower then following calls. If you use the menu, the delays are the same. So nothing I can do about it. And... on my PC it's fast enough that I don't think I didn't press the correct button. Ah yes, and the sound feedback tells you, that a key is selected.If you want to, I could implement a key to jump to the search. It seems to be possible. But, as I said before, think twice if you really need it, the plugin should not get overloaded with keys. And, what is even more important, the keys may not have a function in MP, including "Yes" / "No" shortcuts. As the shortcuts are different in every language, you can run easily into trouble. The keys have to be free as I don't see any possibility for now to "steal" MP the keystrokes. The two routines listen "simultaneously". Hope that makes some things clearer.In a future version, you might be able to assign the keys manually. For now it's been hard-coded.
This is the way MP handles these things. On first call it's a bit slower then following calls. If you use the menu, the delays are the same. So nothing I can do about it. And... on my PC it's fast enough that I don't think I didn't press the correct button. Ah yes, and the sound feedback tells you, that a key is selected.
If you want to, I could implement a key to jump to the search. It seems to be possible. But, as I said before, think twice if you really need it, the plugin should not get overloaded with keys. And, what is even more important, the keys may not have a function in MP, including "Yes" / "No" shortcuts. As the shortcuts are different in every language, you can run easily into trouble. The keys have to be free as I don't see any possibility for now to "steal" MP the keystrokes. The two routines listen "simultaneously". Hope that makes some things clearer.
In a future version, you might be able to assign the keys manually. For now it's been hard-coded.