View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000765 | Spring engine | General | public | 2008-01-03 16:25 | 2011-05-22 16:17 |
| Reporter | tvo | Assigned To | abma | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000765: ArchiveMover.exe should behave more like default windows file dragging | ||||
| Description | In my opinion, ArchiveMover.exe should make a somewhat smart choice between either copying or moving the file: 1. Move if source location is on Desktop or in Temp. 2. Move if source and destination location are on same disk partition. 3. Copy if source and destination location are on different disk partitions, unless 1 applies. This would make it more usable in combination with moving maps/mods around on USB mass storage devices or network locations. | ||||
| Tags | No tags attached. | ||||
| Checked infolog.txt for Errors | |||||
|
|
i'm not sure if doing different thing depending on a rather obscure rules is a good idea. imho we should favor consistency; a decision whether to copy/move/ask could be made by the user in settings.exe. |
|
|
2 + 3 is now implemented, imo 1. is also to platform specific... 1. will make more problems if implemented: what to do with existing files, currently they are renamed. i think the user has to copy itself, the program can't guess what the user wants to do. |
