marcocorvi / topodroid

TopoDroid code base
https://sites.google.com/site/speleoapps/
GNU General Public License v3.0
54 stars 26 forks source link

When importing zip files with wrong filename, offer to try to import ignoring filename #92

Closed rsevero closed 9 months ago

rsevero commented 9 months ago

Is your feature request related to a problem? Please describe. It's frustrating when trying to import zip files in Topodroid and get a "invalid manifest file" only because the filename was changed from _Surveyname.zip to _Surveyname (1).zip or something similar

Describe the solution you'd like Topodroid could present the expected name available in the manifest file and offer ot import despite the zip filename not being the same as the one in the manifest file.

marcocorvi commented 9 months ago

requirement that survey name matches zip name was not enforced in the code for a long time.

On Mon, Feb 12, 2024, 11:36 PM Rodrigo Severo @.***> wrote:

Is your feature request related to a problem? Please describe. It's frustrating when trying to import zip files in Topodroid and get a "invalid manifest file" only because the filename was changed from Survey_name.zip to Survey_name (1).zip or something similar

Describe the solution you'd like Topodroid could present the expected name available in the manifest file and offer ot import despite the zip filename not being the same as the one in the manifest file.

— Reply to this email directly, view it on GitHub https://github.com/marcocorvi/topodroid/issues/92, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACXMYC53PMUTSLHQY2ELZWLYTKKOXAVCNFSM6AAAAABDFP57AKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTCMJQG42DSNY . You are receiving this because you are subscribed to this thread.Message ID: @.***>

rsevero commented 9 months ago

Humm, maybe the person that reported that to me did something else with the zip file. I will check. Sorry for the confusion.

Tapter commented 9 months ago

I once noticed the same behavior back in topodroid 6.1, however I haven't seen it happening on 6.2 - probably it has been fixed since