1) Just to confirm, when you say "download the file to the browser", does that mean setting `streaming: true`? Also, there were number of significant performance improvements for searching in version 3.0. We'd recommend updating to 3.0 if you are not using it already.
2) Could you provide us with the document and the search terms that reproduces this issue?
3) You can edit ReaderControl.js to add custom events. For this particular case, you can add event fires in fullTextSearch function as follows:
fullTextSearch: function(pattern) {
this.fireEvent('searchStarted');
...
me.docViewer.textSearchInit(pattern, mode, true,
function(result) {
...
} else if (result.resultCode === Text.ResultCode.e_done) {
...
me.fireEvent('searchEnded');
}
And you can listen to those events in config.js as follows:
$(document).on('searchStarted', function() {
// show spinner
});
$(document).on('searchEnded', function() {
// hide spinner
});
Justin Jung
Software Developer
PDFTron Systems Inc.