[Feature Request] Add "Ask User" / "Always prompt for save location" option for scanned document exports

[DeSynkro]

Hey there Pynicolas! Hope you're doing well.
I really love this app,it's become my go-to for scanning documents. I have one small request if it's at all possible to be implemented.

On the App settings there's a way to change the Export Folder, which is awesome. However, I'd love the ability to choose "Ask User" (or "Prompt every time") as an export option.

For every batch I scan, I prefer to manually select the destination folder on my device. This is especially useful when I scan different types of documents (receipts, contracts, personal papers, etc.) that belong in different folders.

Would this be something that can be implemented?

Thank you so much for your time.

[alerque]

This is a bit of a variant on a similar use case I opened #218 to consider.

[DeSynkro]

This is a bit of a variant on a similar use case I opened #218 to consider.

I suppose so. Honestly I just want to be able to manually select where to save the documents I scan.
Everything else about this app is perfect for me :)

[alerque]

I'm not saying my proposed interface would be ideal for your use case: it likely wouldn't. I'm just noting that both are in the same general problem space. We both want to target different kinds of scans with different settings. You want to pick a different location every time while keeping other settings the same. I'd rather not pick every time and have it go to the right place from the get-go and I also want other settings to go with the different places.

An idea to cover both use cases might be to have the settings actually manage output profiles, and by default only have one just like it is now, but with at option to "add export profile". This would allow you to enter a new set of image settings and output location. Then when hitting save from a scan if there was more than one profile it could prompt for which profile to use.

[pynicolas]

@DeSynkro Thank you for your kind words.
I think I understand the use case. And indeed, it seems slightly related to #218.
I'll keep it in mind, but I don't have plans for this at the moment.