Bug 312872 - automatically close notification after a timeout/interaction
Summary: automatically close notification after a timeout/interaction
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 2.1
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
: 321528 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-01-08 10:52 UTC by Siddhartha
Modified: 2013-06-24 08:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.11.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Siddhartha 2013-01-08 10:52:26 UTC
Won't it be better if the notifications, which currently opens in a red bar below location, automatically close after a timeout, or maybe after some interaction from user.

Reproducible: Always

Steps to Reproduce:
any notification such as folder cannot be dropped into itself
Actual Results:  
notification appears a in red bar, and does not disappear unless closed manually

Expected Results:  
notification should be removed after some time
Comment 1 Jekyll Wu 2013-01-08 11:42:17 UTC
Yeah, I like this idea, especially after entering a wrong path in the location bar then entering the correct path.
Comment 2 Frank Reininghaus 2013-01-08 12:21:10 UTC
Thanks for the report! Funny, I've also recently thought about the question if we really need the message widget to stay until the user closes it.

A timeout as the disadvantage that we would have to choose some value, and there would always be users who would think that it is too long or too short. Moreover, the widget could then be closed while the user is doing something else in the view, which might be annoying.

Therefore, I think it might be best to close the widget when the URL of the view changes. Would you agree that this is a good solution?
Comment 3 Siddhartha 2013-01-08 12:38:38 UTC
That is a step in the right direction, of course. But what about cases like "Folder cannot be dropped into itself". User will likely continue working on the same directory for a while. Can we think of what to do in cases like this?
Comment 4 Frank Reininghaus 2013-01-08 18:22:25 UTC
> That is a step in the right direction, of course. But what about cases like
> "Folder cannot be dropped into itself". User will likely continue working on
> the same directory for a while. Can we think of what to do in cases like
> this?

Right, a URL change won't help there. But I still think that a timeout-based hiding of the widget is a no-go. Consider that the entire contents of the view move when the widget is hidden - this can be very annoying if it happens surprisingly while the user just tries to click an item in the view.

Another option to deal with the "Folder dropped on itself" message would be to just remove it, and forbid such drops, indicated by the "drop forbidden" indicator.
Comment 5 Frank Reininghaus 2013-05-12 08:03:51 UTC
Git commit 5324fcd315a78f7f2f7ae59bb78a5029e3951674 by Frank Reininghaus.
Committed on 12/05/2013 at 10:01.
Pushed by freininghaus into branch 'master'.

Hide the message widget when the URL changes

Most error messages are only relevant when trying to open a URL, e.g.,
they inform the user that opening the URL failed. After the next
successful URL change, these errors are not relevant any more.
Therefore, it makes sense to hide the message widget automatically to
prevent that the user is forced to close it manually.
FIXED-IN: 4.11.0
REVIEW: 110369

M  +1    -0    dolphin/src/dolphinviewcontainer.cpp

http://commits.kde.org/kde-baseapps/5324fcd315a78f7f2f7ae59bb78a5029e3951674
Comment 6 Frank Reininghaus 2013-06-24 08:02:17 UTC
*** Bug 321528 has been marked as a duplicate of this bug. ***