Slows down Notepad++ very much when you have a lot of documents open

[stedvol-14]

I love this plugin but the whole program (Notepad++) becomes very, very slow when you have a lot of documents open (thousands). This is due to NavigateTo as the problem is gone when I rename NavigateTo.dll. With v2.8, every time I switch to another document or close a document, i.e. when I'm not even directly interacting with the plugin, it takes a couple seconds to display the text content of the new document that's in focus.
So I prefer using v1.12.7, which is only slow when I actually use the plugin (and it doesn't affect the performance of Notepad++ itself when I'm not using the plugin). The first time I use the search function in a while, it first takes a few seconds and crashes. Then when I try again it's fast.

[young-developer]

@stedvol-14 Can you try to enable disable different settings on plugin`s settings page? @molsonkiko implemented pulling and caching at some point maybe there is something related to the settings or cache time.

[stedvol-14]

I see no settings that sound relevant in v2.8 and there is no settings page in v1.12.7
With v2.8, every time I switch to another document or close a document, i.e. when I'm not even directly interacting with the plugin, it takes a couple seconds to display the text content of the new document that's in focus.

[young-developer]

@stedvol-14 can you send a screenshot of your settings page?

[molsonkiko]

This is almost certainly a result of the caching I implemented. The specific source of the latency described is probably this block of code, which reloads the file list in response to a variety of actions. As a reminder, the purpose of this change was to avoid loading the file list every time the user types into the form, which would have even more severely limited the utility of the plugin.

@stedvol-14
This behavior should only happen when the form is visible. So if you hide the form with the X button in the top right corner, the plugin should not do this search whenever you change files. If you continue to get this latency even when the form is hidden, I would be very surprised (as the code indicated above is clearly meant to avoid reloading in such a case) and that would be a serious bug. You could also probably uncheck the Keep dialog visible setting (under General in the top left) to make it so that the form does not automatically open when you start up Notepad++.

@young-developer
In principle it ought to be possible to defer this caching behavior until the user interacts with the form. You can't really do the caching in response to a key press, because the user can use the form without typing in the search box, and the user should always be looking at an up-to-date file list when they interact with the form. So you'd have to create a flag that toggles from false to true whenever caching is currently being executed, move the caching code into a block that, when an appropriate event occurs and if the flag is true, runs that caching code and sets the flag to false.

[young-developer]

@molsonkiko Thank you for review I will check the code.

@stedvol-14 Here is my settings page tested with 206 files and version: 2.7.1.0

[young-developer]

@stedvol-14 I added additional release with reload debounce. Check settings and try different values. I set default value to 300ms but 3000ms could be acceptable value as well. Hope it partially resolve the issue.
https://github.com/young-developer/nppNavigateTo/releases/tag/v.2.8.1

P.S. Honestly for the best experience rendering should be reimplemented to some sort of virtual grid and dont reload all grids rows and records at once but it requires more time for reimplementation and testing.

[young-developer]

@stedvol-14 If you want you can try some experimental build with more aggressive optimizations: https://ci.appveyor.com/project/young-developer/nppnavigateto/build/job/lqdpk8bx0iiteal3/artifacts