timer.py: revert change needed for recordtimer add own doActivate to recordtimer
fix recordings from deepstandby when the current channel must be stopped because of lacking resources
small optimizations and cleanups by Moritz Venn
small speedups/cleanups by moritz venn
add code to simulate recordings (with faked frontends) now its more easy to build a timer overlap detection or similar
move function to better place
add support for cyclic garbage collection to eTimer and eSocketNotifier class, add simpler method to set a timer callback.. or remove.. instead of timer.timeout.get().append(func).. or .remove(func)... now it is possible to do timer.callback.append(func)... timer.callback.remove(func) (the old method still works..but is now deprecated)
better debug info
cleanup some imports
added a "Starting on" option to set a starting date for repeated timers
just increase timer event endtime in processrepeated when begintime is equal to endtime
change addOneDay to work correctly on non existing dst changing times
shorten addOneDay method by using python stuff
hopefully fix the daylight saving problem for repeated timers
move getNextRecordingTime to correct place, no more crash when try to change a running sleeptimer
a zap timer is not a record timer (this fixes the no more working e2 shutdown when a zap timer has zapped but the nowtime is smaller than the event endtime
add ability to stop currently running repeated timer when disabling it
some python import cleanups lesser swig overhead
daylight saving fix, thanks to pieter
revert change from april '06 resaons: adding currently running event as repeated timer doesn't start till the next repeated event occurs breaks changing repeated timers while they run please report side effects