| Summary: | Permanent data loss due to unexpected behavior (autohiding notifications of file operations can be confusing) | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | sreque <seanthenewt> |
| Component: | notifications | Assignee: | Rob Scheepmaker <rob> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | andresbajotierra, aseigo, faure, notmart, peter.penz19, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
sreque
2009-12-08 07:27:11 UTC
It seems like, if going to support asynchronous command processing with files, you should require the user to explicitly click on a button to background the task. For instance, in Eclipse when doing an update the action occurs in the foreground but you can choose to background it with a single mouse click if you want. I have never seen file manipulation tasks backgrounded in a file explorer program and certainly didn't expect it based on the visual cues I was getting from dolphin, especially the since the estimated transfer time was 0 seconds. That would be a bug in the Plasma notifications (about the file transfer). Sorry about the data loss... So far, I think that the notifications of file operations were modified a bit, hopefully avoiding situations like this. Reassigning I am very much against the "auto hiding" of the job progress notification in plasma too. It's very confusing and unexpected. there is an always-visible progress notification now. |