TTD Forum

Code: Alles auswählen

        DrawLine (rgn, W, N, W, S, ARGB (1, 63, 63, 63));   //W
        DrawLine (rgn, E, N, E, S, ARGB (1, 63, 63, 63));   //E
        DrawLine (rgn, W, N, E, N, ARGB (1, 63, 63, 63));   //N
        DrawLine (rgn, W, S, E, S, ARGB (1, 63, 63, 63));   //S

Code: Alles auswählen

Loop through user's search terms
For every search term:
-If search term is found from EPG data, save that program's information into TAP's memory
 (start time, end time, name (with possible user definable suffix (date etc.)), channel, start padding, end padding, ...)

Loop through the programs that will be timered (found in last loop) to find timers that can not be made
because there is no free tuners. NOTE: No real timers will be done as Topfield timers in this phase. All timer handling is made in TAP's memory.
For every program:
-Check from the beginning of the timer (including start padding) every minutes until the end of the program (including end padding). 
 Check in every minute if there is a free tuner (it has to be the same tuner for the whole program (or part of the program, see more below)).
  -If there is a free tuner for the whole program, fine.
  -If there is no free tuner for the whole program:
    -Check how long time there is a free tuner for the program:
      -If the time length is more than user definable setting [MIN_REC_LENGTH_%],
       let's change recording program's start time as this part's start time (remember possible start padding) and end time as this part's end time.
       Maybe also some kind of extra character could be added into file name (that character says that this file is only part of the program).
       Also log entry should be added into log file.
      -If there is still more than [MIN_REC_LENGTH_%] of the program time left (including end padding) when there were no tuners left anymore,
       let's continue going though the program minute by minute again. If we find another bigger than [MIN_REC_LENGTH_%] part, let's add another timer 
       for that same way we did it above.
      -If there is no [MIN_REC_LENGTH_%] long parts at all, don't create timer at all.
       Write this into log file

Loop through timerable programs found in last loop to check if there will be consecutive timers in same channel 
(check between timers in TAP's memory only (because we will not change timers in Topfield's timer list))
-If there is consecutive timers in timers in TAP's memory:
  -If user definable setting [USE_PADDING_BETWEEN_CONSECUTIVE_PROGRAMS] is true, change latter timer's start time as 
   program start time (from EPG) + previous program's end padding. Then there won't be overlapping timers on same channel.
  -If user definable setting [USE_PADDING_BETWEEN_CONSECUTIVE_PROGRAMS] is false, change latter timer's start time as 
   program start time (from EPG) and previous program's end time as program end time (from EPG). Then there won't be overlapping timers on same channel.

Finally we create timers from TAP's memory into Topfield timer list. 
NOTE: Before this step we have not created timers into Topfield timer list. All timer handlings has been done in TAP memory.
-If all timers can not fit into Topfield timer list, do not add timers that are most in the future. 
 When most future timers are not added, they will most probably be added in the next days' night scans (or when ever TAP does this search suff).
 Should we write this also into log file?



We also need a feature to show log file into user easily. 
This way user can see easily what searches did not create timers. User should see log file's last entry's
date easily so that user would not have to open log file to see if there is new log entrys.

There have to be priority for search terms.

Of course operators (like Jag's not, starting with, ending with and so on) should be supported.

It should be possible to search also from description. Also support for DescriptionExtender TAP!

It should maybe be possible to set how far into the future search terms are searched. 
If they are searched e.g. a week from now then there can be problems if the EPG will change (program move from time X to time Y in EPG).