Bug 195760 - browsing archives does not allow drag and drop, cut, copy and paste
Summary: browsing archives does not allow drag and drop, cut, copy and paste
Status: RESOLVED DUPLICATE of bug 77127
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-09 11:52 UTC by m.wege
Modified: 2017-01-14 14:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2009-06-09 11:52:13 UTC
Version:           1.2.80 (using 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.30-020630rc6-generic

When browsing a zip archive I can not do much apart from browsing through it and copy a file out of the archive. What does not working is draging and dropping a file from out the archive in the archive, moving a file within the archive. Since browsing an archive within Dolphin looks like you within a folder I consider this a bug because it does not give you a feedback that this is not supposed to work. The wish part of this report is: Would be cool if it worked.
Comment 1 Peter Penz 2009-06-09 16:32:31 UTC
Thanks for the report. This restriction was the main reason why browsing through archives is disabled per default: From a technical point of view implementing drag & drop between archives is very difficult - it would be required to zip/unzip archives on the fly, which cannot be done fast enough for doing it synchronously in the scope of a file manager (at least not as part of the used IO slave).

However from a users point of view I fully agree that this would be nice.
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:18:36 UTC
Resetting assignee to default as per bug #305719
Comment 3 Elvis Angelaccio 2017-01-14 14:02:52 UTC

*** This bug has been marked as a duplicate of bug 77127 ***