Forums Feature Suggestions Optimizing /aline speed

When printing text to a custom @window using /aline, it proves to be terribly slow when compared to other options like /loadbuf and /filter.

When /fupdate is set to 0, /echo and /aline are the same speed, but with /fupdate set to 1~100, /echo enjoys a clear speed improvement that /aline does not. (up to 4x faster on my machine, but definitely not instant.)

In either event, both /aline and /echo are especially slow when compared to other options. Is this something that could easily be addressed? In particular, perhaps a switch for /aline and/or /echo that suppresses painting text until a final /aline or /echo command is used? Sort of like /draw* commands enjoy the -n switch for the same reason?

The -n switch prevents the display from being updated immediately. This allows you to make changes to the window in the background and then display the results only when you have finished. You can update the display by using any of the /draw commands with only the window name specified.

No, both of these have been optimized as far as possible. These are as fast as I can make them. In fact, they will likely be slower in future when I change mIRC's display routines to use more modern Unicode APIs, which are far more involved/complex. Apart from that, features like /loadbuf and /filter expect to handle large numbers of lines, so their line loading methods are very different. Such methods cannot be applied to /aline or /echo.