Feature Request - A way to handle long refresh cycles and "not responding" conditions

The Tixati UI is nice and responsive most of the time.  The auto-refresh is mostly good.  However, occasionally it can go into a Not Responding state when in a refresh cycle.  This typically happens when it's trying to perform a complex filter search on a lot of content; especially if the user is using a complex or malformed regex.

Tixati will carry on working once it finishes it's refresh cycle.  The problem is that it jumps right into the next refresh cycle fairly quickly and the user only has a couple of seconds to fix their regex or turn off the filter or whatever.  And there is no visual indication of when the user has control again.

I've been trying to think of a way this could be mitigated without radically changing the Tixati architecture.  One way would be to have a manual refresh mode, but I think that introduces all sorts of problems.  But I had an idea.

When Tixati UI starts a refresh cycle, have it make an internal note of the time.  When it completes the refresh cycle, it looks at the time and if the time spent refreshing has been more than a few seconds, extend the gap between refresh cycles to allow the user more opportunity to edit their filter.  Perhaps the longer it has been stuck in the refresh cycle, the longer it allows between refreshes.  So that will allow the user more time to fix or turn off their filter.

But also give a visual indication of when the next refresh cycle will start when it is in an extended inter-refresh state, like maybe a shrinking green line along the bottom of the filter area.

That will show the user when they are able to edit or turn off their filter as well as showing them how much time they have to do so.  And it would all be automatic.  If refresh times are short enough (fractions of a second), then the UI just behaves as it does now.

Throwing it out there.

All the best.

meson1