id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
20	ratescan: add possibility to change fCounterMax and fResolution during runtime	dneise	somebody	"I think it might be useful to be able to change the values of fResolution and fCounterMax also at runtime, so that long running rate scans can be executed, without the need to restart the program.

I think it is fine to let the user change these values in any state, even in ""InProgress"", similar to CHANGE_STEP_SIZE and the like.

fCounterMax is only used in HandleTriggerRates() and even if the user changes fCounterMax during a ratescan for every step in a crazy way, the results will never be wrong.

The same is true for fResolution. The results will never be wrong, just there will be nothing like a minimal resolution anymore. But since for each point in a ratescan, we do not only store the rate, but also the time, it took to take the point, we have the resolution available for every point. So there is no problem."	enhancement	new	minor		component1