A bunch of bug reports
Posted: 18 May 2009 13:07
Hi,
I've been using XY for a few months now, as Vista's Explorer was just dreadful. I'm overall very happy with it, but have a few bugs to report. My main annoyance is when it comes to accessing shares / UNC paths.
Version: v7.90.0120 @ Vista 64-bit.
1) XY seems just a tad slower than Explorer when browsing shares on relatively slow servers (for example, one placed on an ADSL line in the other end of the country) in general.
2) When attempting to load an invalid share (or any folder, I guess), the entire application freezes. This renders the app unusable until the timeout period has expired. I guess it's not too easy to alter XY to spawn each tab in its own thread, but it'd be great if you could help this.
3) This one is rather nasty. Repro steps:
- Type "\\10.11.12.13\someshare" (or similar valid share) in the location bar, and hit enter to open it.
- Set focus in the location bar, highlight the "11" (after 10.)
- Type "2", for example (attempting to replace the highlighted "11").
Result: XY hangs for 30 seconds, and ends up reverting to the location first entered (in the first repro step).
It seems that XY begins looking for the server as soon as I begin modifying the server name in the string (maybe to determine the little icon that indicates local folder or share?). In Windows Explorer, it works fine.
4) Occasionally after having had timeouts and freezes, XY's entry on the taskbar will have moved to the end of the list, and will be the last item on the taskbar, as if I had just started it. When it happens, I move it back to the front position (using Taskix), but it ends up happening again! Is XY crashing from the share mishaps in bug 4) and restarting, perhaps?
5) Repro:
- Open a tab
- Focus location bar, enter "c:", and press shift+enter
Result: Nothing happens
This might sound a bit odd, but in Windows Explorer, you can press enter with shift held down, and it'll go to "c:". Often, I do this involuntarily, because I still have shift held down from having typed ":" (European keyboard). Could you allow navigation to a folder with shift held down?
6) Two related issues:
6a) If you have the focus to the location bar, Ctrl+T (my bound key to open new tab) doesn't open a new tab.
6b) If you have focus in the location bar and close a tab with hotkey, the location bar is focused and folded down on the recently used tab which then gets focus. I'd prefer if it didn't get folded down, just had focus.
7) Sometimes the type-ahead search (by keyboard) doesn't work for a few seconds after navigating to a folder. It just goes to the first or second item in the list, and you need to wait a bit for it to work.
8 ) On one rare occasion, I couldn't open new folders I created with Ctrl+N in XY. I could open them fine in Windows Explorer, and it was only when I had finally put a file into the folders that I could open them in XY. Strange! Never seen it since, just happened within the span of a few hours.
That's all I have for now. I'm doing a lot of file copying from slow shares at the moment, so for me, bug 3) in particular would be very nice to get fixed, if you can find the source of the problem.
I've been using XY for a few months now, as Vista's Explorer was just dreadful. I'm overall very happy with it, but have a few bugs to report. My main annoyance is when it comes to accessing shares / UNC paths.
Version: v7.90.0120 @ Vista 64-bit.
1) XY seems just a tad slower than Explorer when browsing shares on relatively slow servers (for example, one placed on an ADSL line in the other end of the country) in general.
2) When attempting to load an invalid share (or any folder, I guess), the entire application freezes. This renders the app unusable until the timeout period has expired. I guess it's not too easy to alter XY to spawn each tab in its own thread, but it'd be great if you could help this.
3) This one is rather nasty. Repro steps:
- Type "\\10.11.12.13\someshare" (or similar valid share) in the location bar, and hit enter to open it.
- Set focus in the location bar, highlight the "11" (after 10.)
- Type "2", for example (attempting to replace the highlighted "11").
Result: XY hangs for 30 seconds, and ends up reverting to the location first entered (in the first repro step).
It seems that XY begins looking for the server as soon as I begin modifying the server name in the string (maybe to determine the little icon that indicates local folder or share?). In Windows Explorer, it works fine.
4) Occasionally after having had timeouts and freezes, XY's entry on the taskbar will have moved to the end of the list, and will be the last item on the taskbar, as if I had just started it. When it happens, I move it back to the front position (using Taskix), but it ends up happening again! Is XY crashing from the share mishaps in bug 4) and restarting, perhaps?
5) Repro:
- Open a tab
- Focus location bar, enter "c:", and press shift+enter
Result: Nothing happens
This might sound a bit odd, but in Windows Explorer, you can press enter with shift held down, and it'll go to "c:". Often, I do this involuntarily, because I still have shift held down from having typed ":" (European keyboard). Could you allow navigation to a folder with shift held down?
6) Two related issues:
6a) If you have the focus to the location bar, Ctrl+T (my bound key to open new tab) doesn't open a new tab.
6b) If you have focus in the location bar and close a tab with hotkey, the location bar is focused and folded down on the recently used tab which then gets focus. I'd prefer if it didn't get folded down, just had focus.
7) Sometimes the type-ahead search (by keyboard) doesn't work for a few seconds after navigating to a folder. It just goes to the first or second item in the list, and you need to wait a bit for it to work.
8 ) On one rare occasion, I couldn't open new folders I created with Ctrl+N in XY. I could open them fine in Windows Explorer, and it was only when I had finally put a file into the folders that I could open them in XY. Strange! Never seen it since, just happened within the span of a few hours.
That's all I have for now. I'm doing a lot of file copying from slow shares at the moment, so for me, bug 3) in particular would be very nice to get fixed, if you can find the source of the problem.