Resort on Rename

[Quaraxkad]

I've found a situation where the disabled option "Resort list immediately after rename [Sort and Rename - Rename]" does not seem to be honored. I am able to reproduce the problem with a ::fresh instance of XY, where the above setting is disabled by default. I created a test folder on my C drive, inside a new text file named t.txt. Then another new text file named z.txt, after the rename the list remains in order z,a. This is the expected behaviour. However, if I do the same test on my V drive, which is a mapped network share, the list is immediately resorted to a,z. The same occurs when both creating new files and renaming existing files

Is there another option that affects network locations?

[Quaraxkad]

Can anybody confirm this behaviour, or is it just me?

[highend]

Yeah, happens here as well

[admin]

Not here (Win8.1). Which Windows?

[Quaraxkad]

Win 11 here, and the computer with the shared folder is Server 2008 R2 if that matters. I saw a thread before where you explained how to turn on and view logging for file system messages that triggered resorts or refreshes. Do you want me to do that? I don't remember the commands to do it or what thread I saw that in.

[highend]

Win 10 as the client and the Samba is the share server on NixOS Linux

R:\test is a local drive (a ram disk)
Z:\test is a share mounted as a drive letter

Animation.gif (385.98 KiB) Viewed 5601 times

[Quaraxkad]

Found it. Not sure if it's of any use. I created a file and named it x.txt, then created a file and named it z.txt. In Pane 1 on the C drive, z remained above x. In Pane 2 on the mapped network V drive z moves under x about half a second after naming. Tested using a ::fresh instance.

Code: Select all

        0  -  2022-03-27 10:19:56.514  ---  WatchDir IN: 0 | 1 | C:\test
        0  -  2022-03-27 10:19:56.514  ---  WatchDir OUT: Change detected [Pane 1]: Type 1 (0x1) | 
  Exit1: IsRenaming
  Exit2: path not listed in Pane 2
      325  -  2022-03-27 10:19:56.839  ---  ShellNotify: SHCNE_CREATE: C:\test\New Text File.txt | New Text File.txt >  | 
  --------------------------------------------------------------------------------------------------
    5.172  -  2022-03-27 10:20:02.011  ---  ShellNotify: SHCNE_RENAMEITEM: C:\test\New Text File.txt | New Text File.txt > C:\test\x.txt | x.txt
      905  -  2022-03-27 10:20:02.917  ---  WatchDir IN: 0 | 1 | C:\test
        0  -  2022-03-27 10:20:02.917  ---  WatchDir OUT: Change detected [Pane 1]: Type 1 (0x1) | 
  Exit1: IsRenaming
  Exit2: path not listed in Pane 2
      303  -  2022-03-27 10:20:03.220  ---  ShellNotify: SHCNE_CREATE: C:\test\New Text File.txt | New Text File.txt >  | 
      921  -  2022-03-27 10:20:04.142  ---  ShellNotify: SHCNE_RENAMEITEM: C:\test\New Text File.txt | New Text File.txt > C:\test\z.txt | z.txt
  --------------------------------------------------------------------------------------------------
    3.179  -  2022-03-27 10:20:07.321  ---  WatchDir IN: 1 | 1 | V:\test
        0  -  2022-03-27 10:20:07.321  ---  WatchDir OUT: Change detected [Pane 2]: Type 1 (0x1) | 
  Exit1: path not listed in Pane 1
  Exit2: IsRenaming
      396  -  2022-03-27 10:20:07.717  ---  ShellNotify: SHCNE_CREATE: V:\test\New Text File.txt | New Text File.txt >  | 
    1.330  -  2022-03-27 10:20:09.047  ---  WatchDir IN: 1 | 1 | V:\test
        0  -  2022-03-27 10:20:09.047  ---  WatchDir OUT: Change detected [Pane 2]: Type 1 (0x1) | 
  Exit1: path not listed in Pane 1

      120  -  2022-03-27 10:20:09.167  ---  ShellNotify: SHCNE_RENAMEITEM: V:\test\New Text File.txt | New Text File.txt > V:\test\x.txt | x.txt
      496  -  2022-03-27 10:20:09.663  ---  WatchDir IN: 1 | 1 | V:\test
        0  -  2022-03-27 10:20:09.663  ---  WatchDir OUT: Change detected [Pane 2]: Type 1 (0x1) | 
  Exit1: path not listed in Pane 1
  Exit2: IsRenaming
      429  -  2022-03-27 10:20:10.092  ---  ShellNotify: SHCNE_CREATE: V:\test\New Text File.txt | New Text File.txt >  | 
      508  -  2022-03-27 10:20:10.600  ---  WatchDir IN: 1 | 1 | V:\test
        0  -  2022-03-27 10:20:10.600  ---  WatchDir OUT: Change detected [Pane 2]: Type 1 (0x1) | 
  Exit1: path not listed in Pane 1

      335  -  2022-03-27 10:20:10.935  ---  ShellNotify: SHCNE_RENAMEITEM: V:\test\New Text File.txt | New Text File.txt > V:\test\z.txt | z.txt

[klownboy]

So we are all on the same page (especially me), are we talking about renaming and then clicking on white space or are we talking renaming and pressing enter? For me on local drives, it never resorts unless I hit enter after the rename (with resort immediately after rename). I actually like that distinction since it's helpful to see the file renamed at it's present location before it's moved (resorted).

[Quaraxkad]

I just checked, it resorts in both scenarios, either renaming and pressing enter or renaming and clicking empty space.

[admin]

I tried it in Win10 but could not reproduce it. Tried a fresh instance as well. Cannot do anything.

[highend]

Is auto-refresh the culprit? If I disable it via View - Auto-Refresh

it doesn't do the resorting on the network drive...

[admin]

Auto-Refresh was enabled here.

[Quaraxkad]

I did some experimenting with fresh portable old versions and found that XYplorer 22.60.0200 does *not* exhibit this bahiour; everything after does. Furthing digging in the beta forum thread narrowed it down further, up to xyplorer_22.70.0016_beta_noinstall does *not* exhibit thiss behaviour; xyplorer 22.70.0017_beta_noinstall and later does. There's nothing in the changelog to suggest anything about resorts was changed, but I went back and forth between these two versions multiple times and confirmed it.

Anything more I can do to help locate the issue?

[admin]

That's probably because of this change:
viewtopic.php?p=195192#p195192
It enables Configuration | General | Refresh, Icons, History | Auto-Refresh | Include network locations by factory default.

But even with this enabled I cannot reproduce it here.

[highend]

As long as Configuration | General | Refresh, Icons, History | Auto-Refresh | Include network locations
is ticked, it does the resorting, once it's off, it stops...

What backend is serving your files on your network, Don?