[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    [KDE Usability] Re: Errors handling during file transfer
From:       Lukas <1lukas1 () gmail ! com>
Date:       2011-07-23 13:28:18
Message-ID: CAHtHk47eMB+=-+0VpzMmPrH35KkBQc9Xh7KNjieZYKFB2ZH=Zg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Looks interesting :)

* But how about ability to undo changes if something wrong had gone (like a
transaction or simulating file copying)? Like moving a source code without
at least one file is close to no better than not moving at all.

* The file list on the left. How does it going to perform in case if like
1000 files fails? is there some way to group files or have a filter input?

* [Edit file N properties] [retry]. Could it be done as a single smart
button [Fix and retry], that would work on multiple files/dirs too?

Cheers,
Lukas

[Attachment #5 (text/html)]

Looks interesting :)<br><br>* But how about ability to undo changes if some=
thing wrong had gone (like a transaction or simulating file copying)? Like =
moving a source code without at least one file is close to no better than n=
ot moving at all.<br>

<br>* The file list on the left. How does it going to perform in case if li=
ke 1000 files fails? is there some way to group files or have a filter inpu=
t?<br><br>* [Edit file N properties] [retry]. Could it be done as a single =
smart button [Fix and retry], that would work on multiple files/dirs too? <=
br>

<br>Cheers,<br>Lukas<br>


_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability


[prev in list] [next in list] [prev in thread] [next in thread]