Changed 9 years ago by Marc Alban <marcalban@…>

Marc thanks for the patch, although it's not the preferred solution. I'll commit a better fix soon.

This code needs some serious cleanup as we are triggering multiple list rebuilds when a rule is deleted. Plus we're living in some alternate reality where reschedules apparently take a couple of ms, that's the only reason I can explain calling CountMatches?() immediately after deleting a rule. This screen should be monitoring scheduling events instead and generally should be more intelligent about when to make minimal updates vs expensive re-sorts, list rebuilds etc. I should have done all this when it was ported to mythui but I just didn't have the time to refactor/optimise every single screen.