XYplorer Beta Club

More and more evidence that you need to write your own auto-complete, Don.

Please save us from Windows' insistence on maintaining a lock on the volume's root because at one time we auto-completed paths there!

TheQwerty wrote:More and more evidence that you need to write your own auto-complete, Don.

Please save us from Windows' insistence on maintaining a lock on the volume's root because at one time we auto-completed paths there!

Indeed, it made SNAP now! The days of Windows auto-complete are counted! right after Carnival...

And that's my last word for today -- gotta debug some beers... ALAAAAAAAAAAFFFFFF!!!!!!!!!

I'm getting the same thing (and can only close XYplorer by killing the process) whenever I select "Show icon overlays" and then close the config dialog. v12.20, unregistered version. Please advise.

As a side issue, maybe XYplorer should update the .ini whenever we update the configuration, since I'm losing whatever config changes I previously made in this run when I prevent a normal exit by killing the process.

Thank you,
~William

william wrote:I'm getting the same thing (and can only close XYplorer by killing the process) whenever I select "Show icon overlays" and then close the config dialog. v12.20, unregistered version. Please advise.

Hi and welcome,

you get this when you close the config dialog?! That's remarkable. Do you have a screenshot of this?

Don

admin wrote:you get this when you close the config dialog?! That's remarkable. Do you have a screenshot of this?

How about a video? http://www.youtube.com/watch?v=MGzU22CFm4A

However, upon rebooting Vista I couldn't reproduce it. Wouldn't you know it.

Dark. I see no light there.

After many different attempts, and adjustments, I discovered that it was Windows Explorers' indexing that was causing the problem for me. I turned off all indexing, for all hard drives, and so far after a couple of weeks I have not seen the problem reoccur. There has been no noticeable slowing of the hard drive use, so indexing is nothing more than a gimmick, that has given me months of anguish for no reason.
Maybe this can be taken into account in future versions of XYplorer, so it cannot happen even if Windows Explorer wants to play its little games in the background.
Thanks to Admin for their help, and I hope this information will help in future versions of a wonderful program.

Wow, thanks for the information!

The problem seems to getting more common to the point where the time savings of using XY are outweighed by the delay it takes to hit retry when i have to mover or copy multiple files.

Doesn't seem to occur on local drives. Always happens when moving, copying, or just selecting on local network drives or cloud drives.

Does not occur with Win File Explorer

Doesn't matter which Win 10 machine or version.

I only frequently move Office and pdf files and haven't tested with other files.

Just selecting a file generates the error prompt to retry.

Windows search service is disabled and stopped on local pc.

Windows search service is disabled and stopped on the network drives.

Refresh in XY is not selected.

lenraphael wrote: ↑02 Jan 2020 02:52 The problem ...

Thank you for reopening this old but never resolved issue. I was just trying to open a new thread but found this old thread from 2013.

I'm having this old issue quite often, sometimes multiple times a day. It is not an "other application", it always appears that XYplorer is blocking itself. The only solution is to close XYplorer, wait a second, and start it again. So the blocking disappears.

Hopefully the developer will find some time to resolve this really old but very annoying issue.

Two ideas:

1) Untick Configuration | File Operations | File Operations | Miscellaneous | File operation progress dialog modeless

2) Tick Configuration | File Operations | File Operations | Background Processing | Enable background processing

Thanks! Will try.

It helped a little bit. I don't need to close and re-open XYplorer any more.

But it's still there, see screenshot here: https://www.screencast.com/t/2SWfXYpAqidd

If I click "OK" the process will be finished anyway.

That's a different thing. Something locks your folder, maybe some open file.