Has Selected Items Changed?

[Dustydog]

In the past, haven't a bunch of items selected stayed selected for multiple operations instead of becoming deselected and jumping to the top? Did I miss something in recent changes? I've tried playing with enough options that I'm getting a bit lost at this point. Advice? It seems logical to keep the same things selected for multiple actions...?

Also, is there a way of changing, I suppose, the cache size for cached folder sizes? I've been losing cached folder sizes fairly frequently lately and been forced to wait for it to recalculate (or not) - admittedly, I have many locations with lots of folders, and I do like seeing that size and count column.

[jupe]

In the past, haven't a bunch of items selected stayed selected for multiple operations instead of becoming deselected and jumping to the top? Did I miss something in recent changes? I've tried playing with enough options that I'm getting a bit lost at this point. Advice? It seems logical to keep the same things selected for multiple actions...?

I am not 100% what you are referring to here, or what operations you are performing exactly, but the below was a semi-recent change that might have some influence, depending on what actions you are doing exactly, or how old your ini file is, but it may not be the cause, but I will mention it just in case:

Code: Select all

v18.80.0004 - 2018-03-09 20:54
    + List: In v11.40.0102 - 2012-08-10 09:17 I added this to adapt to the 
      behavior of WinXP's Explorer:
          From now on copies of items created in the same path as the original 
          items (by Duplicate or Paste) are not auto-selected anymore but the 
          selection stays on the original items. This is in accordance with 
          Windows Explorer behavior and indeed makes more sense.
      Now in Win8.1 and later, Explorer changed its behavior: Now it *does* 
      auto-select the copy. To allow you to mimic the new behavior I added this 
      tweak:
        ListSelectOnPasteInSamePath=1
      The factory default is 1 (we want to go with the flow), but upgraders 
      have to manually set it to 1 if they want the new behavior.

Also, is there a way of changing, I suppose, the cache size for cached folder sizes? I've been losing cached folder sizes fairly frequently lately and been forced to wait for it to recalculate (or not) - admittedly, I have many locations with lots of folders, and I do like seeing that size and count column.

Code: Select all

+ Folder Size Cache: Now you can limit the size of the cache, i.e. the 
      number of folders that are cached. Previously the cache size was unlimited 
      and with some users it had grown to incredible sizes which slowed down app 
      startup considerably.
      I decided to limit the cache to 10,000 folders by default. You can tweak 
      this number here to your own needs and liking, e.g. raise it to 50,000:
        CacheFolderSizesMaxCount=50000
      The limiting works like this: On saving the cache from memory to disk, 
      when the number of cached folders is higher than the limit (* see below) 
      then the *oldest* items in the cache are purged (this is possible because 
      each item in the cache carries the date of its last modification).
        (*) To reduce the amount of purging work I added a little optimization: 
        Purging down to the limit only happens when the number of cached folders 
        is higher than 125% of the limit.

PS: You can also exclude some locations from your cache if you want like this:

Code: Select all

    + Folder Size Caching: Added a tweak to exclude specific locations, 
      separated by "|", from Folder Size Caching. For example:
        CacheFolderSizesExclude=F:\Downloads|T:\
      Note that also all sub folders of those locations are automatically 
      excluded.

for instructions on how to tweak:
https://www.xyplorer.com/faq-topic.php?id=tweak

[Dustydog]

Though I'm still not sure what's going on with my selections, I deeply appreciate the time you took. It's something that only happens if the number of files selected exceeds the size of the window vertically (I think). And yes, I've played with the keep in view option, etc. - probably need to try a few more combinations of things.

You saved me a pile of time pointing me straight to what I needed to know about size caching - thank you.

[Dustydog]

Does CacheMaxFolderSizes = 0 still create an unlimited cache? Other than startup time, is this a bad thing to do? (Wish my memory were better - apparently I used to know about that tweak.)

[jupe]

Yeah I am not sure about your selection issue, Don or someone else might have some suggestions for you about that soon. As for the cache, I don't use folder size caching, so I could be wrong, but it is my understanding from the text I supplied above:

I decided to limit the cache to 10,000 folders by default.

means that CacheFolderSizesMaxCount=0 has an internal limit of 10000+125%, so you need to modify as suggested if you want more than that since you say you are hitting that limit. The downsides AFAIK would be disk space & memory usage, and as you already mentioned startup time.