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
MediaPortal 1
MediaPortal 1 Plugins
InputDeviceMapper and LiveDriveIR Configuration Problem
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="kaburke" data-source="post: 11971" data-attributes="member: 11818"><p>In answer to your first question (static pointer), that would be nice, but the application instantiates the other plugins (e.g., LiveDriveIR, etc.) independantly of InputDeviceMapper, so how would I get a handle to it to store it in the first place?</p><p></p><p>Having said that, your second question is quite interesting, and negates the first (sort of). The idea of making the plugins separate from the built-in plugin system strikes me as a good one. Indeed, short of anyone pointing out any reasons why that would be a bad idea, I am going to go ahead and implement it.</p><p></p><p>One final note, not to be nitpicky, but I don't want the InputDeviceMapper to be restricted by misconceptions: the device plugins (e.g., LiveDriveIR, etc.) need not be IR plugins. They could be gameport plugins, keyboard plugins, etc.</p><p></p><p>(I apologize if you understood that already - as I said, I just don't want others getting the wrong impression, and thereby limit the potential usefulness of InputDeviceMapper.)</p></blockquote><p></p>
[QUOTE="kaburke, post: 11971, member: 11818"] In answer to your first question (static pointer), that would be nice, but the application instantiates the other plugins (e.g., LiveDriveIR, etc.) independantly of InputDeviceMapper, so how would I get a handle to it to store it in the first place? Having said that, your second question is quite interesting, and negates the first (sort of). The idea of making the plugins separate from the built-in plugin system strikes me as a good one. Indeed, short of anyone pointing out any reasons why that would be a bad idea, I am going to go ahead and implement it. One final note, not to be nitpicky, but I don't want the InputDeviceMapper to be restricted by misconceptions: the device plugins (e.g., LiveDriveIR, etc.) need not be IR plugins. They could be gameport plugins, keyboard plugins, etc. (I apologize if you understood that already - as I said, I just don't want others getting the wrong impression, and thereby limit the potential usefulness of InputDeviceMapper.) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
InputDeviceMapper and LiveDriveIR Configuration Problem
Contact us
RSS
Top
Bottom