Thanks for your comments.
The main focus of the first implementation of this feature was to minimize lag in the user interface the more messages were printed in mIRC across all windows. It did this by progressively decreasing the display update rate, so as more lines were printed, it would delay the display update to every Nth line, where N would gradually increase.
One reason why I implemented it this way is that it is as independent as possible from how slow/fast the user's computer is. It just kicks in and ramps up.
The second implemention, in the latest beta, changes the algorithm so that:
(1) it calculates the maximum lines per second dynamically - it gradually increases the display update delay until any further delay makes little difference and leaves it at that level. So, for example, if you set a /timer to echo at 250ms, it won't trigger /fupdate. At 10ms, it will. If the timer then changes back to 250ms, /fupdate adjusts automatically. So /fupdate now tries to display text as smoothly as possible based on the lines per second being printed.
(2) Any speed less than 10 lines per second no longer triggers /fupdate.
