Page 1 of 1

Resort after creation, ...

Posted: 28 May 2008 12:00
by jacky
* I have "Resort List after rename" enabled, and it works. So when I create a new file/folder, name it, press Enter, it goes right where it should. That's all good, but if I don't rename the new item, there's no resort done.

Is that on purpose ? Creating new folders without renaming them lately had me a but confused at first by that behavior, and I can't really think of a reason why it should be that way, but maybe I'm missing something??


* When going to a new folder, XY needs to read/scan for all items there, etc

- Why is the List filled, then sorted. I mean, wouldn't it be faster to list everything silently, then show it sorted ? I don't know, it's nothing but every time I see the list filling up, then being sorted afterwards, I wonder if there's not time being "wasted" a little here...

- I would really like a busy/hourglass icon during that operation, because sometimes you don't know if XY is done or not, and especially when you don't actually know what to expect in that location, or are working on a distant machine, it gets confusing : can I do something, or should I still wait ? Is XY done, or not?

Re: Resort after creation, ...

Posted: 28 May 2008 14:45
by admin
1. I changed it: Now, when you ENTER the new-but-not-renamed item it will be resorted. When you ESC it it stays.

2. I'm surprised that you see this regularly. I see it only on large folders on first scan. It has always been like this in XY. To sort a list I need to have the full list first. This can take while, so -- to show that something is going on -- I paint the first items I get from the file system in original NTFS order. I don't paint the whole list, of course, just the part that's visible -- it's very fast, so not much time is wasted. If I would not do this, then on large folders, there would be a notable delay before anything happens in the list. I decided years ago that the current way is better. I'm ready to revise that decision. I might add a tweak to allow you to experiment...

Re: Resort after creation, ...

Posted: 28 May 2008 15:29
by jacky
admin wrote:1. I changed it: Now, when you ENTER the new-but-not-renamed item it will be resorted. When you ESC it it stays.
Okay, cool :)
admin wrote:2. I'm surprised that you see this regularly. I see it only on large folders on first scan. It has always been like this in XY. To sort a list I need to have the full list first. This can take while, so -- to show that something is going on -- I paint the first items I get from the file system in original NTFS order. I don't paint the whole list, of course, just the part that's visible -- it's very fast, so not much time is wasted. If I would not do this, then on large folders, there would be a notable delay before anything happens in the list. I decided years ago that the current way is better. I'm ready to revise that decision. I might add a tweak to allow you to experiment...
Well, "regularly"... yes I do have a few places with thousands of items, and every first time I go there it happens. Also, since I don't go there that often, I think whatever gets cached the first time also gets cleaned after a while, so when I go back within the hour maybe it'll be instant, but if I let a few hours go by, then a "new scan" might be needed.

I think I can say I see it every day. I'm not saying it actually slow things down, I was just curious that's all, but I never doubted that, had it been time-consuming, you wouldn't have let it happen. ;)

As I said using an hourglass pointer during the operation would be nice I think. It seems there's one, but it goes away before everything is really done (or painted?)

About the tweak, I think it would be a nice thing actually yes, because I also use XY on a computer I connect to using RDC, and when I do that the drawing operation isn't really as fast as locally quite obviously, so I can see the List being drawn one time, first rows, middle rows, last rows, and then again once ordered, first rows, middle, and last ones. For those times a "no first painting" tweak might help a little yes.

Re: Resort after creation, ...

Posted: 28 May 2008 15:37
by admin
jacky wrote:As I said using an hourglass pointer during the operation would be nice I think. It seems there's one, but it goes away before everything is really done (or painted?)
:? goes away too early? weird... you do special stuff like folder size calc or thumbs?

I added that tweak: now you choose. :)

Re: Resort after creation, ...

Posted: 28 May 2008 15:48
by jacky
admin wrote: :? goes away too early? weird... you do special stuff like folder size calc or thumbs?
nope, Details view without CFS (I do that on-demand only), but sometimes I can see the hourglass go away before everything is actually done/painted.
I'm not sure of the specifics, but for example I know that when I change folders on my "RDC-XY", I can see the hourglass, Tree gets repainted, the hourglass goes away and only then is List being painted...
admin wrote:I added that tweak: now you choose. :)
Excellent :D Thanks!

Re: Resort after creation, ...

Posted: 28 May 2008 15:52
by admin
jacky wrote:
admin wrote: :? goes away too early? weird... you do special stuff like folder size calc or thumbs?
nope, Details view without CFS (I do that on-demand only), but sometimes I can see the hourglass go away before everything is actually done/painted.
I'm not sure of the specifics, but for example I know that when I change folders on my "RDC-XY", I can see the hourglass, Tree gets repainted, the hourglass goes away and only then is List being painted...
Tree and List have each their own hourglass logics. What you describe can happen with lots of tree work and then a relatively short list. XY does the tree first, then removes the tree's hourglass (if any), then starts filling the list. If this takes longer than 500 msecs a new hourglass is shown for the list and taken away when the list is done.

Re: Resort after creation, ...

Posted: 01 Jun 2008 16:59
by jacky
admin wrote:Tree and List have each their own hourglass logics. What you describe can happen with lots of tree work and then a relatively short list. XY does the tree first, then removes the tree's hourglass (if any), then starts filling the list. If this takes longer than 500 msecs a new hourglass is shown for the list and taken away when the list is done.
Well, I'm still thinking I've seen the hourglass go away before the List was filled, and it was longer than 500ms. Maybe it was also always when I have a VF on, because I know last time was, and I think I often have one as I find myself wondering whether or not XY is done, or just filtering...

Either way, now with the little tweak it's perfect, so I'm good :D
Thanks!