Reply to thread

Message

You are indeed limited to the actions defined by MediaPortal. Ideally plug-ins should be able to publish their own actions so that they can be mapped to shortcuts, thus each plug-in would not need to implement its own key mapping system, they could just use the MP1 system. For now and until actions can be published, if your plug-in is interested in the keys it should not use the action handler. It should instead get the keys from the system (WM_INPUT) and possibly use SharpLibHid to parse the message much like Auto3DPlugin does.

Hard coding shortcuts in plug-in is bad practice

<blockquote data-quote="Stéphane Lenclud" data-source="post: 1189389" data-attributes="member: 140174">You are indeed limited to the actions defined by MediaPortal. Ideally plug-ins should be able to publish their own actions so that they can be mapped to shortcuts, thus each plug-in would not need to implement its own key mapping system, they could just use the MP1 system. For now and until actions can be published, if your plug-in is interested in the keys it should not use the action handler. It should instead get the keys from the system (WM_INPUT) and possibly use <a href="https://www.nuget.org/packages/SharpLibHid/" target="_blank">SharpLibHid </a>to parse the message much like <a href="https://forum.team-mediaportal.com/threads/auto3d-plugin-for-mediaportal-1-2-1-12-gui-tv-beamer.116708/" target="_blank">Auto3DPlugin </a>does.Hard coding shortcuts in plug-in is bad practice <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="Stéphane Lenclud, post: 1189389, member: 140174"] You are indeed limited to the actions defined by MediaPortal. Ideally plug-ins should be able to publish their own actions so that they can be mapped to shortcuts, thus each plug-in would not need to implement its own key mapping system, they could just use the MP1 system. For now and until actions can be published, if your plug-in is interested in the keys it should not use the action handler. It should instead get the keys from the system (WM_INPUT) and possibly use [URL='https://www.nuget.org/packages/SharpLibHid/']SharpLibHid [/URL]to parse the message much like [URL='https://forum.team-mediaportal.com/threads/auto3d-plugin-for-mediaportal-1-2-1-12-gui-tv-beamer.116708/']Auto3DPlugin [/URL]does. Hard coding shortcuts in plug-in is bad practice :) [/QUOTE]