XYplorer Beta Club

If that's the case, and I'm not mistaken, you could use this tweak to show the list after it's loaded, right?

; Tweak: set to 1 to display new List contents only after all items have been retrieved and sorted
NoDisplayBeforeSort=1

Which may fix the problem?

That makes it much more snappy and easy to work with, thanks

AlexanderM wrote:

If that's the case, and I'm not mistaken, you could use this tweak to show the list after it's loaded, right?

; Tweak: set to 1 to display new List contents only after all items have been retrieved and sorted
NoDisplayBeforeSort=1

Which may fix the problem?

That makes it much more snappy and easy to work with, thanks

On further investigation, it doesn't actually help it much. Maybe a little bit.

It'd be great if you could look into it, as it greatly hinders fast browsing with type-ahead searching of file and folder names. I want to be able to type the split-second I open a folder.

To repeat, try going into a folder such as c:\windows, and immediately write "system32". The selection should go to the system32 folder (as it's the first item in the folder with such a name), but most likely, XY won't begin catching your keystrokes until after a few characters.

AlexanderM wrote:

AlexanderM wrote:

If that's the case, and I'm not mistaken, you could use this tweak to show the list after it's loaded, right?

; Tweak: set to 1 to display new List contents only after all items have been retrieved and sorted
NoDisplayBeforeSort=1

Which may fix the problem?

That makes it much more snappy and easy to work with, thanks

On further investigation, it doesn't actually help it much. Maybe a little bit.

It'd be great if you could look into it, as it greatly hinders fast browsing with type-ahead searching of file and folder names. I want to be able to type the split-second I open a folder.

The last letter must be typed when the list is completely loaded. It's not possible otherwise because it's the typing itself that triggers the search. Other than that the type-ahead is as live as can be. You can find items in the list while the list is still loading. But of course you cannot find items that are not yet loaded.

The last letter must be typed when the list is completely loaded. It's not possible otherwise because it's the typing itself that triggers the search. Other than that the type-ahead is as live as can be. You can find items in the list while the list is still loading. But of course you cannot find items that are not yet loaded.

I guess the bug then is that type-ahead triggers before the list is fully loaded, even with the tweak. I can't see that it's very useful, unless you frequently browse gigantic directories where you'll for some reason want to type-ahead search ASAP (which might only sometimes find your file). Do you disagree with me that it's a bug? Or maybe "undesirable feature"?

AlexanderM wrote:

The last letter must be typed when the list is completely loaded. It's not possible otherwise because it's the typing itself that triggers the search. Other than that the type-ahead is as live as can be. You can find items in the list while the list is still loading. But of course you cannot find items that are not yet loaded.

I guess the bug then is that type-ahead triggers before the list is fully loaded, even with the tweak. I can't see that it's very useful, unless you frequently browse gigantic directories where you'll for some reason want to type-ahead search ASAP (which might only sometimes find your file). Do you disagree with me that it's a bug? Or maybe "undesirable feature"?

Well, what's better? What's expected. What's the standard? I could easily change it to trigger only after loading is completed.

admin wrote:Well, what's better? What's expected. What's the standard? I could easily change it to trigger only after loading is completed.

From my view, it depends on at least three variables: 1) Size of directory 2) Speed of system 3) User typing speed

And a higher value in one of these could be offset by a low value in another, such as for me, a large folder is offset by my hunt-n-peck typing ...so I don't see the present setup as a bug but rather as a feature that may not work ideally for all users...because if we had to wait for list to load, that would impact those users who are comfortable with existing way...and if you had to wait, that would totally defeat ability to "I want to be able to type the split-second I open a folder" which we know isn't possible in all cases.

Related question: is there a specific visual indicator that list is fully loaded and ready to search? It may be obvious but I'm not thinking of it right now.

on the other hand: why would anyone want to search in a folder that is not fully loaded yet (which means that there could be still files missing that would be found by the search). I'd say that the search should be only triggered after the list is complete.

j_c_hallgren wrote:Related question: is there a specific visual indicator that list is fully loaded and ready to search? It may be obvious but I'm not thinking of it right now.

Of course: as long as the list is loaded the standard arrow includes the small hourglass. Additionally the statusbar reflects the changes in number of items and size and "flashes" a little bit when finished.

Pagat wrote:Of course: as long as the list is loaded the standard arrow includes the small hourglass. Additionally the statusbar reflects the changes in number of items and size and "flashes" a little bit when finished.

I've not noticed it (AFAIK) before because the folders that I use tend to have small nbr of items, and even on larger folders, I'm never in that much of a hurry, I guess.

admin wrote:Well, what's better? What's expected. What's the standard? I could easily change it to trigger only after loading is completed.

I know it's probably a hated argument to bring up, but try it with the standard Windows Explorer. Even if you begin typing the instant you enter a folder (with the enter key, and have your hands ready on the keyboard), it always works.

It kinda seems that it caches your keystrokes even if it is in the process of loading the list. You can try opening c:\windows, then entering system32, and immediately type "qua" as fast as you can. Even if you type while the list is loading and the list window is white/blank, it'll go to "quartz.dll" when the list has been loaded (which takes maybe 0.5-1 seconds depending on your system).

For really gargantuan folders (>5000 items?), Windows Explorer begins displaying items before the list is fully loaded. In this case, I'd say that allowing type-ahead search before the list is fully loaded would be good. But for relatively few items (below a couple thousand), I'd definitely prefer that it waits until the list is fully loaded.

Thanks for listening . I do a lot of work with folder structures that are the same with different data in them, so I navigate lots of folders where I know the names of the sub-folders and filenames, and I type very fast.

Edit: It also often happens even with folders containing just a few items, strangely.

AlexanderM wrote:

admin wrote:Well, what's better? What's expected. What's the standard? I could easily change it to trigger only after loading is completed.

I know it's probably a hated argument to bring up, but try it with the standard Windows Explorer. Even if you begin typing the instant you enter a folder (with the enter key, and have your hands ready on the keyboard), it always works.

It kinda seems that it caches your keystrokes even if it is in the process of loading the list. You can try opening c:\windows, then entering system32, and immediately type "qua" as fast as you can. Even if you type while the list is loading and the list window is white/blank, it'll go to "quartz.dll" when the list has been loaded (which takes maybe 0.5-1 seconds depending on your system).

For really gargantuan folders (>5000 items?), Windows Explorer begins displaying items before the list is fully loaded. In this case, I'd say that allowing type-ahead search before the list is fully loaded would be good. But for relatively few items (below a couple thousand), I'd definitely prefer that it waits until the list is fully loaded.

Thanks for listening . I do a lot of work with folder structures that are the same with different data in them, so I navigate lots of folders where I know the names of the sub-folders and filenames, and I type very fast.

Edit: It also often happens even with folders containing just a few items, strangely.

Should work in next version.