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
Auto3D plugin for MediaPortal 1.2 - 1.12 (GUI & TV/Beamer)
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="Stéphane Lenclud" data-source="post: 1167716" data-attributes="member: 140174"><p>It's up to each application to decide that. Singleton are usually a bad idea though but that's basically the workaround I suggested earlier quoted below.</p><p></p><p></p><p></p><p>What we really need though in MP is something like this:</p><p></p><p></p><p></p><p>MP should take care of user input mapping into actions. Plug-ins only need to be able to register and react on actions.</p><p>So you would have a workflow like that:</p><ul> <li data-xf-list-type="ul">Auto3D register 'Show 3D menu' action.</li> <li data-xf-list-type="ul">User needs to map that action through any of the Input Handler he is using.</li> <li data-xf-list-type="ul">User hit the button mapped to 'Show 3D menu' action.</li> <li data-xf-list-type="ul">MP does the mapping and issue the corresponding action.<br /> </li> <li data-xf-list-type="ul">Auto3D needs to implement an action handler to trigger the menu.</li> </ul></blockquote><p></p>
[QUOTE="Stéphane Lenclud, post: 1167716, member: 140174"] It's up to each application to decide that. Singleton are usually a bad idea though but that's basically the workaround I suggested earlier quoted below. What we really need though in MP is something like this: MP should take care of user input mapping into actions. Plug-ins only need to be able to register and react on actions. So you would have a workflow like that: [LIST] [*]Auto3D register 'Show 3D menu' action. [*]User needs to map that action through any of the Input Handler he is using. [*]User hit the button mapped to 'Show 3D menu' action. [*]MP does the mapping and issue the corresponding action. [*]Auto3D needs to implement an action handler to trigger the menu. [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Auto3D plugin for MediaPortal 1.2 - 1.12 (GUI & TV/Beamer)
Contact us
RSS
Top
Bottom