abu baniaz
Moderator
While the iron is hot, can we code a fake recording timer so we don't have to use EPG refresh plugin?
What's wrong with using a PowerTimer?While the iron is hot, can we code a fake recording timer so we don't have to use EPG refresh plugin?

While the iron is hot, can we code a fake recording timer so we don't have to use EPG refresh plugin?

If TV was awake and on another service, it should zap back at end.
If it was in deep or regular standby, it should return to standby unless interrupted by zapping onto another service or a recording kicking in.

For a conflict check to be conducted, both start and end times must exist. In the absence of both, that tuner will be unavailable indefinitely for validation purposes.
Except for the selection of a service this is exactly what a "Wakeup" "Power" timer does. This is why I am suggesting that "Zap" type timers may be appropriately moved to the "Power" timer area.How about a compromise, if possible?
ie an option to either just zap (and forget about it - ie open ended - do nothing else after this specific zap event) or zap for a specific time period (user defined)?
This would surely resolve both angles? Either way, as ADM has mentioned, a timer conflict check should be done to avoid potential timer conflict!
I have used them in the past and they are now broken in that they don't hold the tuner and they don't properly appear in the EPG.That seems unlikely, given that there is no way to set an end time for a Zap timer. I don't recall there ever being so (but never use them, so ....).
Set a Power timer for time x and a Zap timer for time x+1.How do you use a power timer to activate a channel without switching on the display on the receiver?
If you have two tuners (or the two channels can be recorded from one at the same time) then the current conflict code will pass such a situation as OK.@ADM's finding prove that there is an error in the current functionality. There needs to be some conflict awareness.
But they do not. Look at the menu that sets them - there is no option to set a time extent.My understanding is that a zap timer should have a start and an end. User can end it at will without being locked into that zap.
The current code is based on the assumption that there is a user sitting in front of it and all that they wish to do is to ensure the channel switches as a start of a programme they wish to watch. So they don't miss the start.If TV was awake and on another service, it should zap back at end.
It does. It just doesn't do what you want it to.The conflict check doesn't seem to work when setting two zap timers for the same time.
Power timers are there to affect the power state of the box (On, Standby, DeepStandby).Except for the selection of a service this is exactly what a "Wakeup" "Power" timer does. This is why I am suggesting that "Zap" type timers may be appropriately moved to the "Power" timer area.
What release of Vix was this on? Or (roughly) when?I have used them in the past and they are now broken in that they don't hold the tuner and they don't properly appear in the EPG.
# if the timer type is a Zap and no end is set, set duration to 1 second so time is shown in EPG's.
if self.timerentry_justplay.value == "zap":
if not self.timerentry_showendtime.value:
end = begin + (config.recording.margin_before.value*60) + 1
As this would be considered a lesser priority timer than a "Record" or "Watch" timer the only conflict checking required would be to see, at the time of the timer firing, if there is a tuner free to display the service. If there is, use it. If not then the current service can't be selected. This is a simplistic conflict check and is all that should be required.Yes, there is. As you need to have a tuner available for the time at which the Zap occurs.