Hello!

Daniele Forsi has written on Sunday, 22 December, at 21:23:
>2013/12/22 Andrej N. Gritsenko:

>> Thank you very much. "Interrupted" looks more appropriate there. How
>> about if I insert exact (not abstract) operation there, such as:

>> "Copying file operation was interrupted and some errors were encountered"

>> Would that look correctly?

>I would change "and" with "because"

No, this case exactly requires "and" - the message is shown after user
press "Stop" button and interrupted the operation. If there were no
errors before then window with progress bar will just close. The phrase
above will be shown if some errors happened before user interrupted the
operation so "and" is correct.

>> Also there is another icorrect sentence in there:

>> "The file operation is finished, but there are some errors."

>> I think it should look similar to one above but with another verb.

>errors such as lack of permissions on some files don't interrupt the
>copy of other files, so when the two messages are displayed?

First one as I said - when user pressed "Stop" button. Second one - when
the operation was finished to let user see what problems were encountered
with it.

>I would try to minimize the differences between the progress window
>and the failure window, if you keep the title "Copying files" you
>don't need to repeat it in the error message, less work for
>translators :-)

Well, as I said - the "Copying" ("Trashing", "Changing attributes of",
etc.) is my intention to keep, it's why I asked how to merge it with
errors notice above.

>see your unmodified progress3 beside a copy and paste with failure3
>http://picpaste.com/progress-failure3b.png

I thought about that. I just did not redesigned it so much radically, I
think the original approach was to show error message at the top of the
window, and also common HIG suggest we should put the most relevant info
at the top.

>do we need to keep the progress bar in the failure case? I suppose
>that it always reaches 100% unless the user pressed Stop

I think it should be good to let it stay, user can see how much was done
before he or she interrupted it.

>Daniele Forsi

    Andriy.

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list

Reply via email to