Pause before opening drives in tree pane

[Stilez]

When I move up and down the tree with the keyboard, drives that aren't connected (network computers I'm not logged into, floppy drives etc) immediately freeze XY while they try and access, rather than waiting for a few hundred milliseconds first (as on Windows Explorer) in case I quickly skip past them to another tree row.

Every time I go from C: to \User it has to go past A:\ and tries to access it. Same applies in going between other drives (past my DVD) or between local drives and a networked computer or 2 networked computers (if another networked computer is in between and not accessible).

(Holding down the up/down key as was suggested in the original thread, fails - it doesn't move the item for ~0.5 - 1 second, then it moves it too quickly to fine tune up or down the 2 or 3 lines needed.)

Windows Explorer accesses on KeyUp plus a wait of ~ 500 ms to confirm there's been no further movement. It works fine and avoids this problem. Is it possible for XY to do the same (or at least do the same if the keyboard was used to navigate to a new item - a different drive - on the tree)?

[admin]

I don't think a wait of ~ 500 ms would be a positive user experience, especially since it can be expected that in the majority of cases the folder or drive *is* available.

[nas8e9]

I don't think a wait of ~ 500 ms would be a positive user experience, especially since it can be expected that in the majority of cases the folder or drive *is* available.

Would it be an idea to special-case removable drives (something XYplorer already knows)?

[admin]

I don't think a wait of ~ 500 ms would be a positive user experience, especially since it can be expected that in the majority of cases the folder or drive *is* available.

Would it be an idea to special-case removable drives (something XYplorer already knows)?

I would not like this. Others?

[avsfan]

I don't think a wait of ~ 500 ms would be a positive user experience, especially since it can be expected that in the majority of cases the folder or drive *is* available.

Would it be an idea to special-case removable drives (something XYplorer already knows)?

I would not like this. Others?

I haven't run into this issue, but it sounds like a reasonable idea...

[Stilez]

I don't think a wait of ~ 500 ms would be a positive user experience, especially since it can be expected that in the majority of cases the folder or drive *is* available.

But in the cases it isn't, it's extremely annoying. The cases where a drive may be slow to respond include:

• Floppy drives
• CD/DVD/Blu-Ray drives
• Networked computers and mapped network drives

In these cases any attempt to keyboard navigate from drive (or device) 1 to drive (or device) 2 going past one of these, the computer or session can freeze for seconds - each and every time. That's extremely annoying.

As well, a user who presses UP-UP in quick succession (<200 ms) in a way that would skip past some drive or device, is surely not interested in opening the intermediate drive, so it's unlikely to affect user experience in any but a positive way.

Perhaps an .ini setting ("delay before opening a drive following KEYUP, in milliseconds") would be worthwhile. It's very unlikely to be other than a positive experience.

I don't think a wait of ~ 500 ms would be a positive user experience, especially since it can be expected that in the majority of cases the folder or drive *is* available.

Would it be an idea to special-case removable drives (something XYplorer already knows)?

I would not like this. Others?

Agree - not something I'd like. Some removable drives are quickly and readily accessible, some are not; ditto some fixed drives.

[avsfan]

As well, a user who presses UP-UP in quick succession (<200 ms) in a way that would skip past some drive or device, is surely not interested in opening the intermediate drive, so it's unlikely to affect user experience in any but a positive way.

Perhaps an .ini setting ("delay before opening a drive following KEYUP, in milliseconds") would be worthwhile. It's very unlikely to be other than a positive experience.

This is exactly what I was thinking when I mentioned that I thought it would be a reasonable idea (though looking back, that's not how I read it now...)

I think the user-configurable delay would be a good way to handle it.

[admin]

I made up my mind and now think it is a good idea. I checked out Explorer and estimated 300 msecs delay there (XP SP3), and took the same amount for XY. Works nicely. Good feature!

[Stilez]

Thanks!!

[Stilez]

Works like a charm!