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
Improvement Suggestions
Improved Weekly / Daily recording algorithm
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="Broceliande" data-source="post: 154885" data-attributes="member: 20120"><p>Hi dvdfreak, </p><p>Behind this fuzzy logic aren't only solvable issues , lemme explain it in a few words , hopefully i'll be clear enough :</p><p></p><p>Let's base on your first message in there :</p><p></p><p></p><p></p><p>This function was designed to do so . Daily , weekly etc schedules are intended to start at xx:xx hours , stop at yy:yy , regardless of the title .</p><p></p><p>Your changes changed the behavior of some schedules types , wich was initially designed in another way ( not telling about code design or so)</p><p>This also changed the logic we use to splitt any type so that we can fix or improve one without thinking about all the other cases .</p><p></p><p>While i was fixing the back2back issues i really could realize how splitting any recording type is important .</p><p></p><p>We planned adding new features in scheduler a long time ago, like a 'closer' based title comparison or other usefull ones .</p><p>Some of them will be added for sure, once other issues are solved .</p><p>Some users wanted to test and use your code and i put it in svn .</p><p>However, in regard of further stuff we kept aside and because of issues we wanted to kick out , i reverted those. Hopefully you won't feel frustated or offensed , the main reason wich made me choose to do so is that it changes too much things in a row on the initial behaviors we were expecting for those schedules .</p><p>However , i won't mind at all if you keep an updated dll in there with your changes/improvements .</p><p>This way we can satisfy the users who want to keep using it</p></blockquote><p></p>
[QUOTE="Broceliande, post: 154885, member: 20120"] Hi dvdfreak, Behind this fuzzy logic aren't only solvable issues , lemme explain it in a few words , hopefully i'll be clear enough : Let's base on your first message in there : This function was designed to do so . Daily , weekly etc schedules are intended to start at xx:xx hours , stop at yy:yy , regardless of the title . Your changes changed the behavior of some schedules types , wich was initially designed in another way ( not telling about code design or so) This also changed the logic we use to splitt any type so that we can fix or improve one without thinking about all the other cases . While i was fixing the back2back issues i really could realize how splitting any recording type is important . We planned adding new features in scheduler a long time ago, like a 'closer' based title comparison or other usefull ones . Some of them will be added for sure, once other issues are solved . Some users wanted to test and use your code and i put it in svn . However, in regard of further stuff we kept aside and because of issues we wanted to kick out , i reverted those. Hopefully you won't feel frustated or offensed , the main reason wich made me choose to do so is that it changes too much things in a row on the initial behaviors we were expecting for those schedules . However , i won't mind at all if you keep an updated dll in there with your changes/improvements . This way we can satisfy the users who want to keep using it [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
Improved Weekly / Daily recording algorithm
Contact us
RSS
Top
Bottom