Delete photos option should be easily accessible
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rapid Photo Downloader |
Fix Released
|
Wishlist
|
Damon Lynch |
Bug Description
This is a wish-list bug (gui related)
I am often using RPD to get pictures from other people's cameras (RPD is extremely handy here as it can sort pictures based on camera type and make). Normally I keep the "delete photos" option enabled. I wouldn't wont to delete photos from other people's memory cards however. It is a bit cumbersome to enable/disable this option. Another issue is that you are not sure what will happen to the pictures as there is no visual indicator of the mode shown. Wouldn't it be better to have it somewhere in a more accessible place? File menu? A tick on the bottom of the list (next to download buttons)? The additional benefit is the fact the you see the option is on which might be important if the card you are getting pictures from is not yours...
Related branches
Changed in rapid: | |
assignee: | nobody → Damon Lynch (dlynch3) |
milestone: | none → 0.4.3 |
status: | Triaged → In Progress |
Changed in rapid: | |
status: | In Progress → Fix Committed |
Changed in rapid: | |
status: | Fix Committed → Fix Released |
This is an interesting observation. You definitely have a good point here - the feature is not as user friendly as it could be. These are some core python philosophies which help guide me in the program design, and I think in this case you've identified that "explicit is better than implicit" is not being followed as well as it could be:
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Another way to think about it: when a camera has never been seen before, the program could pop up a warning dialog that auto delete is enabled. Please think about such scenarios in the context of different workflows, and then how you envisage such a feature. Please add it to this bug report.