Option: ask for extraction location

sereko / theunarchiver

Automatically exported from code.google.com/p/theunarchiver

Other

0 stars 0 forks source link

Option: ask for extraction location #158

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

It is nice having the option to ask for destination on each extraction, but it 
annoying to ask at the start of the extraction?

Lets say I have multiple big archives ready to extract, each taking 5+ minutes 
to extract. I start by queueing them up. Then 5 min 
from now I am interrupted with a sheet/dialog asking for a destination. I think 
it would be nice to ask for the destination when the 
archive is queued, not when extraction starts. That way I can queue a bunch of 
extractions up and let TheUnarchiver do its thing 
without being interrupted intermittently to choose a destination folder.

What version of the product are you using? On what operating system?

The Unarchiver v2.0 alpha 4, OS X 10.5.7 (build 9J3050)

Original issue reported on code.google.com by joe.roback@gmail.com on 29 Jun 2009 at 11:59

GoogleCodeExporter commented 9 years ago

If you queue up multiple archives in one click, this shouldn't happen. I guess 
it might happen if you go through 
the list and click them one by one? Is that the case?

Original comment by paracel...@gmail.com on 30 Jun 2009 at 1:01

GoogleCodeExporter commented 9 years ago

yea, the archives are all in different directories. i start one going, browse 
to the next archive (while the current 
one is extracting), then queue the next one, and so forth and so on.

Original comment by joe.roback@gmail.com on 30 Jun 2009 at 1:05

GoogleCodeExporter commented 9 years ago

Yes, I can see that this needs to be handled more smoothly one way or the other.

Original comment by paracel...@gmail.com on 2 Jul 2009 at 12:50

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Original comment by paracel...@gmail.com on 2 Jul 2009 at 12:50

Added labels: Priority-Medium, Type-Enhancement

GoogleCodeExporter commented 9 years ago

Man, this sure ended up being a lot more work than I thought it would be to 
fix, but at least the code structure 
is now cleaned up and makes much more sense.

Original comment by paracel...@gmail.com on 9 Jul 2009 at 2:18

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Wow. excellent news :-)

Original comment by joe.roback@gmail.com on 9 Jul 2009 at 3:07