[janbar]

I notice that recent versions of your doityourself branch (since 538416d Aug 13th) don't adjust the 'start' time of a repeating timer to use 'next recording' / 'last recorded' anymore.

I liked the way rules which were going to do something appeared above 'now' and those that had done something in the past appeared at the time they last did it. This made it much easier to keep track of my long list of repeating timers.

The message which goes with commit 538416d says "This commit preserve rule timeslot against bad overriding when user update the timer". I guess this means there was a conflict with editing a timer, but I don't understand what or why.

If there's a problem I'd like to try and find a fix so the addon can use 'next recording' / 'last recorded' again.

Can you explain?

Before this commit , RULE with valid timeslot (not "any time") was overriden with next or last recorded. On user update the timeslot was updated with these wrong values, also next or last recorded include margin start and we cannot determine the right end time.
My conclusion is RULE with valid timeslot cannot be overriden because RULE have to be the mirror of backend RULE, and only RULE without timeslot (any time) can be overriden.