Reply to thread

Message

I didn't expect the bug to disappear completely. The question is however, do you think the bug occurs less frequent now?

With the new DLL the keyboard hook has been optimized to use as little time as possible. The main change is that the mapped action is performed asynchronously, outside of the hook.

The hook is still running in the context of the main MediaPortal UI thread however. So, if MP is busy doing something on the main UI thread when you press a key, the main thread first has to finish what it's doing before the hook can be invoked. If the hook cannot be invoked in time, it will still be disabled.

As discussed before, I can try to run the hook on another thread with its own message loop. However, I'm not sure whether I will be able to block key events being sent to the main MP UI thread in that case. If I cannot block the key events, each key press will be handled by both the plug-in and MP.

<blockquote data-quote="rsenden" data-source="post: 811939" data-attributes="member: 24295">I didn't expect the bug to disappear completely. The question is however, do you think the bug occurs less frequent now?With the new DLL the keyboard hook has been optimized to use as little time as possible. The main change is that the mapped action is performed asynchronously, outside of the hook.The hook is still running in the context of the main MediaPortal UI thread however. So, if MP is busy doing something on the main UI thread when you press a key, the main thread first has to finish what it's doing before the hook can be invoked. If the hook cannot be invoked in time, it will still be disabled.As discussed before, I can try to run the hook on another thread with its own message loop. However, I'm not sure whether I will be able to block key events being sent to the main MP UI thread in that case. If I cannot block the key events, each key press will be handled by both the plug-in and MP.</blockquote>

[QUOTE="rsenden, post: 811939, member: 24295"] I didn't expect the bug to disappear completely. The question is however, do you think the bug occurs less frequent now? With the new DLL the keyboard hook has been optimized to use as little time as possible. The main change is that the mapped action is performed asynchronously, outside of the hook. The hook is still running in the context of the main MediaPortal UI thread however. So, if MP is busy doing something on the main UI thread when you press a key, the main thread first has to finish what it's doing before the hook can be invoked. If the hook cannot be invoked in time, it will still be disabled. As discussed before, I can try to run the hook on another thread with its own message loop. However, I'm not sure whether I will be able to block key events being sent to the main MP UI thread in that case. If I cannot block the key events, each key press will be handled by both the plug-in and MP. [/QUOTE]