Opened 16 years ago
Closed 16 years ago
#1873 closed defect (fixed)
DirectUpload plugin chooses its own upload filename for the GPX track, not the real filesystem name
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Plugin | Version: | latest |
| Keywords: | Cc: |
Description
The DirectUpload plugin pics its own auto-generated filename for traces (see this upload). Instead it should use the filename for the GPX trace by default and allow the user to change it via a text field.
Attachments (3)
Change History (9)
comment:1 by , 16 years ago
| Version: | → latest |
|---|
comment:2 by , 16 years ago
follow-up: 4 comment:3 by , 16 years ago
| Priority: | major → minor |
|---|
comment:4 by , 16 years ago
Replying to xeen:
What's the advantage over simply adding a description?
The user may use his own naming scheme for traces, and the expected behavior of web interfaces (or the things that use them) is to by default use the original filename, not make up a new one.
Anyway, FWIW until something like this is implemented I won't use this plugin, opting instead to use the web interface instead where the filenames I usually use for my traces won't be munged.
by , 16 years ago
| Attachment: | viking-upload-osm.png added |
|---|
How the Viking OSM upload dialog is structured
by , 16 years ago
| Attachment: | viking-upload-osm-fixed.png added |
|---|
[FIXED] How the Viking OSM upload dialog is structured
by , 16 years ago
| Attachment: | directupload-long-filename.png added |
|---|
DirectUpload plugin dialog broken with long GPX file names
What's the advantage over simply adding a description?