AFAIK broce did remove the fuzzy stuff from svn since it broke things in other places and he had no fast solution for fixing these. Maybe try to meetup with him on irc before doing any double/unnecessary work.
AFAIK broce did remove the fuzzy stuff from svn since it broke things in other places and he had no fast solution for fixing these. Maybe try to meetup with him on irc before doing any double/unnecessary work.
I just got the latest version from SVN and the code still seemed to be in there.
Attached is a possible fix. I was able to fix it very locally and basically added the logic I described earlier: the closest program to the original schedule time is recorded, the other one isn't. All this only in case the next and/or previous program have the same title of course.
My change is untested, but I thought it best to send it in as quickly as possible because if I needed to thoroughly test this first it could be a few weeks And I'm sure you (and others) will be happy to try it out.
Like MP works out of the box is very simple: record every week from 22:00 until 23:00, whatever the program at that time.
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 :
Like MP works out of the box is very simple: record every week from 22:00 until 23:00, whatever the program at that time.
This function was designed to do so . Daily , weekly etc schedules are intented 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 issue 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, one 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
dvdfreak of course we'd be interested if someone would like to team up with e.g. Broce to centralize and clean up all code. This would allow a safer expansion of features in the future...
However keep in mind that at some point Bavarian's personal epg might get finished (it's already in svn and most likely would have to be changed accordingly) and render this discussion useless
But OK, I guess I will indeed have to keep patching my own local copy of MP then.
Present is to fix the existing issues , and indeed there is some redundant code in MP.
Future will tell about possible new features like yours or others.
Btw , the most often , we don't only wanna record a show wich plays 'around' xx:xx , but rather any show of this series .
For that we have 2 kind of schedules already :
"Record always on this / on every channels"
But OK, I guess I will indeed have to keep patching my own local copy of MP then.
I even said you could keep it up to date here for the users who wanna use it.
Ah, OK, interesting, what is this exactly? A plugin that replaces the current scheduler?