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
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
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="framug" data-source="post: 1286907" data-attributes="member: 19448"><p>As said, your proposal is interesting.</p><p>Therefore, there are already many settings in MP1 and, this complicate code because, some options could interfere with others.</p><p>A newer option could be interesting but, only, if it doesn't break the existing MP process.</p><p>I don't think adding a newer option only because "let's users choose" is a good way if, this option breaks the compatibility.</p><p>What happen (for example in DB) if users check this and uncheck it after ?</p><p>When checked, what with all MP functions and all plugins (integrated or third) ?</p><p>For me, you can propose a newer setting to let users choose only, if it change what you are supposed to improve but, without others side effects.</p><p>You have a setting example with multi tuner grab EPG, not integrated yet (choose if single tuner grab or, parallel tuners) without none effect with the rest of process.</p><p>And yes, this is a pain and, we have to break our a*s each time to make it possible.</p></blockquote><p></p>
[QUOTE="framug, post: 1286907, member: 19448"] As said, your proposal is interesting. Therefore, there are already many settings in MP1 and, this complicate code because, some options could interfere with others. A newer option could be interesting but, only, if it doesn't break the existing MP process. I don't think adding a newer option only because "let's users choose" is a good way if, this option breaks the compatibility. What happen (for example in DB) if users check this and uncheck it after ? When checked, what with all MP functions and all plugins (integrated or third) ? For me, you can propose a newer setting to let users choose only, if it change what you are supposed to improve but, without others side effects. You have a setting example with multi tuner grab EPG, not integrated yet (choose if single tuner grab or, parallel tuners) without none effect with the rest of process. And yes, this is a pain and, we have to break our a*s each time to make it possible. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
Contact us
RSS
Top
Bottom