Reply to thread

Message

One main difference between the two DLL versions is that the original version passed keys through to MediaPortal if a mapping was defined for that key, but none of the mapping conditions were met. The new version simply doesn't pass through any keys that have been defined in the mapping, regardless of whether any mapping conditions are met or not.

According to your log, the Enter key is defined in the KeyboardInputPlugin mapping, so with the second DLL this key is never passed through to MediaPortal. I guess this key was passed on to MP in the original plug-in because none of the conditions in this mapping were met.

I could re-introduce the original behavior, but that means (a little bit) more processing code inside the hook, so a (slightly) higher chance that the hook times out. As an alternative, you can add a 'No Condition' -> 'Select Item' action to the Enter key mapping in KeyboardInputPlugin.

I would like to know the opinion of other users on this matter; should the plug-in pass through any keys for which none of the conditions are met, or should the plug-in simply intercept all keys defined in the mapping, irregardless of conditions?

<blockquote data-quote="rsenden" data-source="post: 811877" data-attributes="member: 24295">One main difference between the two DLL versions is that the original version passed keys through to MediaPortal if a mapping was defined for that key, but none of the mapping conditions were met. The new version simply doesn't pass through any keys that have been defined in the mapping, regardless of whether any mapping conditions are met or not.According to your log, the Enter key is defined in the KeyboardInputPlugin mapping, so with the second DLL this key is never passed through to MediaPortal.&nbsp; I guess this key was passed on to MP in the original plug-in because none of the conditions in this mapping were met.I could re-introduce the original behavior, but that means (a little bit) more processing code inside the hook, so a (slightly) higher chance that the hook times out. As an alternative, you can add a 'No Condition' -&gt; 'Select Item' action to the Enter key mapping in KeyboardInputPlugin.I would like to know the opinion of other users on this matter; should the plug-in pass through any keys for which none of the conditions are met, or should the plug-in simply intercept all keys defined in the mapping, irregardless of conditions?</blockquote>

[QUOTE="rsenden, post: 811877, member: 24295"] One main difference between the two DLL versions is that the original version passed keys through to MediaPortal if a mapping was defined for that key, but none of the mapping conditions were met. The new version simply doesn't pass through any keys that have been defined in the mapping, regardless of whether any mapping conditions are met or not. According to your log, the Enter key is defined in the KeyboardInputPlugin mapping, so with the second DLL this key is never passed through to MediaPortal. I guess this key was passed on to MP in the original plug-in because none of the conditions in this mapping were met. I could re-introduce the original behavior, but that means (a little bit) more processing code inside the hook, so a (slightly) higher chance that the hook times out. As an alternative, you can add a 'No Condition' -> 'Select Item' action to the Enter key mapping in KeyboardInputPlugin. I would like to know the opinion of other users on this matter; should the plug-in pass through any keys for which none of the conditions are met, or should the plug-in simply intercept all keys defined in the mapping, irregardless of conditions? [/QUOTE]