home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Products
IR Server Suite (IRSS)
IMON & MCE at the same time - AbstractRemoteModel enabled or disabled
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="chefkoch" data-source="post: 961766" data-attributes="member: 10438"><p>The Abstract Remote's purpose is to prevent having different mappiing for different remote at the MediaPortal mapping level. You only map the Imon buttons to the abstract remote. So the MP mapping can be used by all Remotes without modifying it.</p><p> </p><p>What you are suggesting would open the door to do the same for other remotes as well, but then it is no abstract remote mapping anymore.</p><p>If you would like to use the a different mapping at the same time like the abstract remote, you can</p><p>a) remove the imon to abstract mapping in "IR Server\Abstract Remote Maps\iMon USB" or</p><p>b) disable the abstract remote completely.</p><p> </p><p>i.e. the Imon PAD.xml looks currently like this:</p><p>[CODE=XML] <RemoteTable RawCode="1002" AbstractButton="Power" /></p><p> <RemoteTable RawCode="1016" AbstractButton="Power2" /></p><p> <RemoteTable RawCode="1064" AbstractButton="Record" /></p><p> <RemoteTable RawCode="1128" AbstractButton="Play" /></p><p> <RemoteTable RawCode="1114" AbstractButton="Eject" /></p><p> <RemoteTable RawCode="1130" AbstractButton="Rewind" /></p><p> <RemoteTable RawCode="1144" AbstractButton="Pause" /></p><p> <RemoteTable RawCode="1192" AbstractButton="FastForward" /></p><p> <RemoteTable RawCode="1066" AbstractButton="NextChapter" /></p><p> <RemoteTable RawCode="1220" AbstractButton="Stop" /></p><p> <RemoteTable RawCode="1208" AbstractButton="PreviousChapter" /></p><p> <RemoteTable RawCode="1148" AbstractButton="OK" /></p><p> <RemoteTable RawCode="1038" AbstractButton="VolumeUp" /></p><p> <RemoteTable RawCode="1042" AbstractButton="VolumeDown" /></p><p> <RemoteTable RawCode="1022" AbstractButton="ChannelUp" /></p><p> <RemoteTable RawCode="1014" AbstractButton="ChannelDown" />[/code]</p><p>Removing this abstract mapping will forward "imon : 1128" (remote : code) to the receivers(MPControlPlugin) instead of Play.</p><p>With the same result like sending "Abstract-imon : 1128".</p><p>The same can be achieved by disabling the abstract remote model.</p><p> </p><p>Having such a "specific" use case, where you need to differ between remote, the abstract remote model should be disabled. It's not the responsibility of the abstract remote model to differ between remotes.</p></blockquote><p></p>
[QUOTE="chefkoch, post: 961766, member: 10438"] The Abstract Remote's purpose is to prevent having different mappiing for different remote at the MediaPortal mapping level. You only map the Imon buttons to the abstract remote. So the MP mapping can be used by all Remotes without modifying it. What you are suggesting would open the door to do the same for other remotes as well, but then it is no abstract remote mapping anymore. If you would like to use the a different mapping at the same time like the abstract remote, you can a) remove the imon to abstract mapping in "IR Server\Abstract Remote Maps\iMon USB" or b) disable the abstract remote completely. i.e. the Imon PAD.xml looks currently like this: [CODE=XML] <RemoteTable RawCode="1002" AbstractButton="Power" /> <RemoteTable RawCode="1016" AbstractButton="Power2" /> <RemoteTable RawCode="1064" AbstractButton="Record" /> <RemoteTable RawCode="1128" AbstractButton="Play" /> <RemoteTable RawCode="1114" AbstractButton="Eject" /> <RemoteTable RawCode="1130" AbstractButton="Rewind" /> <RemoteTable RawCode="1144" AbstractButton="Pause" /> <RemoteTable RawCode="1192" AbstractButton="FastForward" /> <RemoteTable RawCode="1066" AbstractButton="NextChapter" /> <RemoteTable RawCode="1220" AbstractButton="Stop" /> <RemoteTable RawCode="1208" AbstractButton="PreviousChapter" /> <RemoteTable RawCode="1148" AbstractButton="OK" /> <RemoteTable RawCode="1038" AbstractButton="VolumeUp" /> <RemoteTable RawCode="1042" AbstractButton="VolumeDown" /> <RemoteTable RawCode="1022" AbstractButton="ChannelUp" /> <RemoteTable RawCode="1014" AbstractButton="ChannelDown" />[/code] Removing this abstract mapping will forward "imon : 1128" (remote : code) to the receivers(MPControlPlugin) instead of Play. With the same result like sending "Abstract-imon : 1128". The same can be achieved by disabling the abstract remote model. Having such a "specific" use case, where you need to differ between remote, the abstract remote model should be disabled. It's not the responsibility of the abstract remote model to differ between remotes. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
IR Server Suite (IRSS)
IMON & MCE at the same time - AbstractRemoteModel enabled or disabled
Contact us
RSS
Top
Bottom