The Ubuntu community has contributed 13716 ideas, 65290 comments, 1273844 votes
Idea
#10909: Nautilus should perform file operations in a separate tread
|
| |
249
|
|
|
Written by Nxx the 9 Jul 08 at 09:18.
Category: System.
Related to:
Gnome.
Status: New
|
|
|
Description
When triing to access bad-burned CD or an FTP site, connected by a weak link, Nautilus temporarily hangs. You cannot click icons and even the contents of the Nautilus' windows not refreshed, so they display garbage. It would be much nicier if such operations were performed in a separate tread than the user interface-related stuff. The contents of the window can display "Please wait, operation is being performed" or show a clock image instead of garbage that is displayed now.
The Windows Explorer show the same problematic behavior, but even worse in that it also incorporates the taskbar in the same tread, so when stuck with file operations, even the taskbar is not responsive.
Attachments
No attachments.
Duplicates
Comments
|
Sidney wrote on the 9 Jul 08 at 11:50
|
But a new thread won't diminish the problems: What good is a file navigator, if he doesn't display any files. And just outsourcing to a new thread won't make it any faster.
Just posting a "please wait" message could be done in one thread before Nautilus tries to open the directory. But I'm not sure if such a message were better: If it can open the dirs quickly, you have a flashing "wait" message. And deciding if the dir can be opened quickly or not is not possible without opening it.
Best solution is to just speed nautilus up ;-).
|
|
Nxx wrote on the 9 Jul 08 at 12:33
| |
How can you speed up unreliable connections, bad written media etc?
|
|
gmatht wrote on the 9 Jul 08 at 13:09
| |
So e.g. currently even the back button doesn't work if the thread hangs. Sounds that could be fixed by a separate thread.
|
|
braaivleis wrote on the 9 Jul 08 at 14:58
| |
A separate thread with a progress listener updating the GUI thread is a more correct way of doing it.
|
|
jpka wrote on the 10 Jul 08 at 06:36
| |
I mean not 'like this' but 'related to this'. Anyway, Ubuntu need more work on handling i/o errors or weak links, in both filelist displaying and file operations.
|
|
korvins wrote on the 24 Jul 08 at 09:44
|
Specially when files are remote! If you open a location which is remote it will take ages, and finally it will say "error".
|
|
Bender2k14 wrote on the 28 Jul 08 at 19:44
|
I agree with this idea. If I try to preform some action that is unresponsive, I would like a way to cancel it, stop it, and go back. I believe that requires a separate thread.
+1
|
Post your comment
|
|
|
