For very large files, like the java doc api (around 40M) resizing the window takes a considerable amount of time. I uploaded a patch file in the Patches section of the website with my hack to solve this.
Basically, I cached the list control width (used to display indexed terms), which computation seems to be quite expensive. Since the index changes only when a new file is opened, it makes sense to compute this value a single time. Before, the list was asked to compute it's 'desired' width at each window resize, which boiled down to the extent of its longest string. Apparently, GetTextExtent is not trivial :))
Thanks for your contribution. I applied the patch.
Log in to post a comment.