Detect constant stream of file events & suggest disabling auto-refresh?

A few people complain that SourceTree refreshes constantly - this is actually not our fault but another app constantly writing data into the repo and triggering a refresh via the file events. We usually advise them to disable the auto-refresh for this repo or generally.

Perhaps we should try to detect this file event flood and suggest disabling the auto-refresh. The trouble is there can be good reasons for the flood to happen temporarily such as running builds, so we don't want to identify those incorrectly. The difference is usually that when you're building SourceTree is in the background so isn't actually refreshing but is receiving the file events to perform a refresh when you next switch back.

Maybe we should only detect this flood of refreshes when the app has the focus and especially when they're trying to commit? We don't have the same 'flood' protection we do on the Mac version so that might be a first step, although it doesn't stop the problem happening on Mac sometimes too (e.q. tools like Qt Designer).