[ChannelSelection] Editing "next" instant timer is not handled correctly

[prl]

If REC>Record next is used to create a recording timer for the next show on a service, and then REC>Change next timer is used to edit the recording to have a start time in the past, the recording is not started. In fact none of the processing should be done when a timer's start/end times are changed is done in the code.

Replication steps

From live TV, FAV to enter the Channel Selection screen.

On any service without a current recording, use REC>Record next to start an instannt recording for the next event on the service (don't use REC, GREEN, that doesn't work see Bug #524).

Then use REC>Change next timer>Edit timer to enter the Timer Entry screen for the timer (again, don't use coloured buttons for selection).

Change the timer Start time to a short time in the past, the OK to save the timer.

EXIT from the Channel Selection screen, then TIMER to enter the timer list.

The modified start time is shown, but the timer state will still be "waiting".

[Peter Urbanec]

Fix bug #526: [ChannelSelection] Editing "next" instant timer is not handled correctly

[ChannelSelectionEPG] Add new method finishedEdit() to correctly handle changes to a timer when it has been edited.

Add finishedEdit() as a completion callback when a TimerEntry screen is opened.

→ <<cset eb424e9158f8>>