| Summary: | never import current collection | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Pierre Hanser <hanser> |
| Component: | Usability-Ergonomy | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version: | 5.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.2.0 | |
| Sentry Crash Report: | |||
|
Description
Pierre Hanser
2018-02-10 16:32:07 UTC
Why should not it be possible? It could also be images outside the collection on the USB drive that you want to import. I do not think we can stop it either. Then it would also have to be prevented that it is not possible to import the collection via the local path. Maik your use case is of course also valid. what puzzle me often is that the default action behind the import key is the wrong one for me and I always have to think to select one of the sub-menu. And when I do not remember this, it starts reading my main collection and I cannot stop it easily and often I end up killing digikam. I wonder if there should be a default action at all for importing key when there is a choice and I would prefer the default action to be opening the sub-menu After 3 weeks of work, i finally completed the compilation of AppImage using Qt 5.11.3 + QWebkit 5.212. New 6.1.0 pre-release AppImage bundle can be found here (64 bits only for the moment) : https://files.kde.org/digikam/ Please check if this bugzilla entry still valid. Thanks in advance Gilles Caulier digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier it's OK now, thanks a lot |