Opened 12 years ago

Closed 12 years ago

Last modified 8 years ago

#2492 closed Enhancement (invalid)

Open file or folder on opt+doubleclick

Reported by: Voxar Owned by: livings124
Priority: Normal Milestone: None Set
Component: Mac Client Version: 1.75
Severity: Minor Keywords:
Cc:

Description

Would be nice to be able to open a downloaded file, if single-file torrent, or folder from the interface. I suggest opt+doubleclick. Attaching patch

Attachments (1)

opt+click_to_open_file.diff (1.6 KB) - added by Voxar 12 years ago.
patch

Download all attachments as: .zip

Change History (4)

Changed 12 years ago by Voxar

patch

comment:1 Changed 12 years ago by livings124

  • Resolution set to invalid
  • Status changed from new to closed

Thanks for the patch, we really do appreciate it.

Unfortunately, opening data while it still is in Transmission can lead to it changing, resulting in the file being reverted or potentially bad data being uploaded, so I have to reject this.

comment:2 Changed 12 years ago by nevyn

Alternative solution: When a file is alt-double-clicked, pop up an alert describing in at most one sentence why editing files while they are being seeded is a very bad idea. Then, present three buttons: 1) Open, and stop seeding (default) 2) Don't open (esc) 3) Open, but keep seeding (alt)

With a "remember my choice" box, of course.

I believe most people do use the files while they are being seeded today, which is a situation in which Transmission offers no help. This proposal would both inform the user, be invisible for the user who doesn't care, and show the user how the situation can be resolved.

comment:3 Changed 8 years ago by cosmotic

This is a really silly reason not to have this feature. As it stands, I right-click, view in finder, then open from there. It's a lot of extra clicks, and the risk of the data being modified is the same.

I don't see how bad data could be uploaded as the chunks are hashed. Worst case is the other peer discards it. NBD. Maybe Transmission could be updated to verify the chunks before they are sent? Maybe it already does this?

Note: See TracTickets for help on using tickets.