Hi,
I remember that there was a discussion some time ago that VDR would use a new date system for timers that also included a month/year in addition to the day. Or am I mistaken? We sometimes end up having old timers in VDR that we just deactivate but don't delete, and it's very hard to know wether a timer that is set to the "5th" is June 5th or May 5th.
We still use VDR 1.3.18 and I work on a small application that uses SVDRP to get this information using LSTT. Was it so that some newer VDR version had changed the date format used?
Regards, Jan Ekholm
Jan Ekholm wrote:
Hi,
I remember that there was a discussion some time ago that VDR would use a new date system for timers that also included a month/year in addition to the day. Or am I mistaken? We sometimes end up having old timers in VDR that we just deactivate but don't delete, and it's very hard to know wether a timer that is set to the "5th" is June 5th or May 5th.
We still use VDR 1.3.18 and I work on a small application that uses SVDRP to get this information using LSTT. Was it so that some newer VDR version had changed the date format used?
VDR/HISTORY:
2005-03-20: Version 1.3.23
... - The day of a timer is now stored as a full date in ISO notation ("YYYY-MM-DD") in 'timers.conf' and for the result of the SVDRP command LSTT (based in parts on a patch by Roman Krenický).
chakie@smultron.net(Jan Ekholm) 04.06.05 12:42
I remember that there was a discussion some time ago that VDR would use a new date system for timers that also included a month/year in addition to the day. Or am I mistaken?
No. the timers format changes. So there is no way back if you run 1.3.23ff if you did not backup your .conf by your own.,
We sometimes end up having old timers in VDR that we just deactivate but don't delete, and it's very hard to know wether a timer that is set to the "5th" is June 5th or May 5th.
That's solved, but (IMHO) it was no good idea that "single timers" are now deleted after done. Some times i missed a timer (because of work at VDR?) or the recording was broken or only partial due to delays, so it was nice just to pickup the last "once" timer and reactivate it. Too there is the problem that the EPG is not going backwards very much, so no "timer base" could be used if i found a "single timer event" being worth to become a regular timer. Maybe the user should have the chance to generally say: "delete single timer when done autoamtically" or "let the user delete them manually".
We still use VDR 1.3.18 and I work on a small application that uses SVDRP to get this information using LSTT. Was it so that some newer VDR version had changed the date format used?
[vdr] VDR developer version 1.3.23 |- The day of a timer is now stored as a full date in ISO notation | ("YYYY-MM-DD") in 'timers.conf' and for the result of the | SVDRP command LSTT (based in parts on a patch by Roman Krenicky).
Rainer
On Saturday 04 June 2005 14:15, Klaus Schmidinger wrote:
Jan Ekholm wrote:
<lots of stuff>
VDR/HISTORY:
2005-03-20: Version 1.3.23
...
- The day of a timer is now stored as a full date in ISO notation
("YYYY-MM-DD") in 'timers.conf' and for the result of the SVDRP command LSTT (based in parts on a patch by Roman Krenický).
Thanks, I didn't think about looking in that file. The change is very, very welcome as it lets me get rid of 50-100 lines of educated guesswork related to the month/year for a timer. It was worth upgrading for that little change.
Now, one could of course ask nicely for a similar change to LSTR? There only the year is missing, but as some of us store recordings for a long time there will be recordings with "wrong" years sooner or later. VDR itself can get this info from the raw files, but SVDRP users can't. Of course, for recordings this info is mostly only of informational nature, unless one tries to figure out the oldest recordings and clean up with DELR.
-- 'Educational' refers to the process, not the object. Although, come to think of it, some of my teachers could easily have been replaced by a cheeseburger. -- Terry Pratchett, alt.fan.pratchett