Opened 11 months ago

Closed 3 months ago

#18729 closed enhancement (fixed)

Tracker: Drag & drop of a link should create another link

Reported by: waddlesplash Owned by: jscipione
Priority: normal Milestone: R1/beta5
Component: Applications/Tracker Version: R1/beta4
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

When dragging and dropping a symlink (e.g. from a virtual directory of Applications) onto the Desktop, presently the target file is copied. Instead, I believe another link should be created.

This would be a behavioral change to something that goes all the way back to BeOS, but I think it'd be the right move. I know I've been burned by this before...

Change History (10)

comment:1 by humdinger, 11 months ago

If I drag&drop a symlink from some folder to another on a different volume, it gets copied. IMO it's only natural if it did the same when doing it from a virtual folder.
So, +1 on this proposal.

How can this be a change from BeOS, when there were no virtual folders in that more simple, innocent times? :)

comment:2 by diver, 11 months ago

I wanted to file the same issue long time ago but I thought there was already one. IMO, it should be moved to beta5 as it is a recurrent issue (at least on Telegram). +1

comment:3 by waddlesplash, 11 months ago

Milestone: UnscheduledR1/beta5

comment:4 by nephele, 6 months ago

Milestone: R1/beta5R1/beta6

comment:5 by waddlesplash, 6 months ago

Milestone: R1/beta6R1/beta5

in reply to:  1 comment:6 by jscipione, 3 months ago

Replying to humdinger:

If I drag&drop a symlink from some folder to another on a different volume, it gets copied. IMO it's only natural if it did the same when doing it from a virtual folder.
So, +1 on this proposal.

How can this be a change from BeOS, when there were no virtual folders in that more simple, innocent times? :)

Tracker copies to different volumes, moves on the same volume like ye old Classic Mac OS (and modern macOS). That explains the BeOS and current behavior even before fancy virtual folders were introduced.

Does this enhancement need to be in the R1B5 milestone?

comment:7 by waddlesplash, 3 months ago

It would be nice if we could get the fix in before beta5 but it's not urgent, we can easily bump to beta6.

comment:8 by chak2025, 3 months ago

Last edited 3 months ago by chak2025 (previous) (diff)

comment:9 by jscipione, 3 months ago

Owner: changed from nobody to jscipione
Status: newin-progress

comment:10 by waddlesplash, 3 months ago

Resolution: fixed
Status: in-progressclosed

Fixed in hrev58030 +beta5.

Note: See TracTickets for help on using tickets.