Hang in there!

[jacky]

Ok, maybe not a bug per-se but I'm reporting it there still because it really can be a pain!!

It seems XY doesn't try to get the Catalog's items icons on startup or anything, but only when they must be shown (for the 1st time). That's a good thing.

But, if you have a bunch of items that points to network locations, that happen to be unavailable at the time, XY will try each one of them (to get the icon) and fail. But that's a pretty slow process, during which XY is unresponsive at all.

I'm not saying there's an easy solution or anything, but one thing that could help maybe is to have something like:
- if this is the third location to be unavailable on a given server or path (eg. \\server\path\) then assume all other locations under such server/path will be unavailable, and inform/or ask- the user about it (maybe).

Because right now it might really look like XY is just gone & lost, and one might not realize what's going on. I didn't at first, and for one path it can take some time, but I happen to have a few of them so it really took some time for XY to get back.

BTW, maybe some kind of special icon, or even just the usual overlay for unavailable path could be used in such case, instead of nothing?

[admin]

I see the problem, and yes, there 's no easy solution because there's no quick way (that I know of -- and I researched this several times) to find out whether a server is availble or not: testing this takes as long as trying to get the icon.

BTW, maybe some kind of special icon, or even just the usual overlay for unavailable path could be used in such case, instead of nothing?

You mean an option "Do not retrieve icons from network locations" (but use some default icon instead)?

[jacky]

I see the problem, and yes, there 's no easy solution because there's no quick way (that I know of -- and I researched this several times) to find out whether a server is availble or not: testing this takes as long as trying to get the icon.

hmm.. does that mean, you can test if the server is available or not, but it takes as long as the icon?
Because if so, maybe sometimes do that instead of the icon! For example, I have like 10 items poiting to different locations on one server. Maybe, if the 2 first ones are unavailable, for the next one test the server first, and then the icon only if the server is indeed there. Otherwise, all items pointing to this server would be known to be unavailable right away...

At least for me, that would speed up things! Since when the server is not there, and XY tries to get the icons, it would be 3 tests (icon 1, icon 2, server) and not 10 !!

Actually, if it's too much I won't complain so much, as I don't face this problem so much. Usually the server is there, and if not it's because it's gone, but XY was already running and doesn't try to get them again, since it got them already.
Besides, they're all in a category usually closed that I only open if I know the server is there. But there's always this time it's gone without telling me , or I forgot to close the category!

BTW, maybe some kind of special icon, or even just the usual overlay for unavailable path could be used in such case, instead of nothing?

You mean an option "Do not retrieve icons from network locations" (but use some default icon instead)?

Well, that could be helpful too. But no, actually I meant to show when XY cannot access the (network) location, and so not get the icon. Right now, it just doesn't show nothing, maybe have the overlay to indicate that this item's destination isn't available.