Remove lag when switching between tabs, especially with network paths
Posted: 29 May 2019 16:07
When I switch to a network-path tab, there is a lag of around 1+ seconds before I can perform another action. This happens even with the network caching option enabled.
This means that if I'm trying to Ctrl-Tab between tabs and one in the middle is for a network path, I have to wait. It gets especially bad when I have multiple network-path tabs open. (And it's also reproducible when using the mouse to switch tabs.)
There is even a small lag when switching to a local-path tab, which you can see by holding Ctrl-Tab down for a few seconds (unless your keyboard repeat rate is set to slow). If you do that, the tabs will continue cycling after you release Ctrl-Tab, because the actions are queued up.
I'm proposing that when switching to a different tab, there should be a short period of time during which the content of that tab is not processed. So if I switch to Tab1, and then switch to Tab2 within, say, 0.1 seconds, there would be no delay in getting to Tab2 - even if Tab1 was an extremely slow network drive. I don't know what the right amount of time would be, but I routinely will quickly press Ctrl-Tab-Tab-Tab etc... to switch between tabs. I think a good test of the "fix" would be that if a user holds down Ctrl-Tab for 5 seconds with a fast keyboard repeat rate, and upon releasing those keys the final XYplorer tab in the sequence is immediately selected.
This means that if I'm trying to Ctrl-Tab between tabs and one in the middle is for a network path, I have to wait. It gets especially bad when I have multiple network-path tabs open. (And it's also reproducible when using the mouse to switch tabs.)
There is even a small lag when switching to a local-path tab, which you can see by holding Ctrl-Tab down for a few seconds (unless your keyboard repeat rate is set to slow). If you do that, the tabs will continue cycling after you release Ctrl-Tab, because the actions are queued up.
I'm proposing that when switching to a different tab, there should be a short period of time during which the content of that tab is not processed. So if I switch to Tab1, and then switch to Tab2 within, say, 0.1 seconds, there would be no delay in getting to Tab2 - even if Tab1 was an extremely slow network drive. I don't know what the right amount of time would be, but I routinely will quickly press Ctrl-Tab-Tab-Tab etc... to switch between tabs. I think a good test of the "fix" would be that if a user holds down Ctrl-Tab for 5 seconds with a fast keyboard repeat rate, and upon releasing those keys the final XYplorer tab in the sequence is immediately selected.