I'd like to have an automated system-check _before_ starting up digiKam. This check should take place in backround, as for example at startup, and/or on request. This check must be able to identify bottlenecks of the systems support, and, therefore, be able to supply recommendations or at least informations to enable the user to react on specific corrections. Reproducible: Always Actual Results: digiKam does not indicate hardware oe software limitations.
Did you have any particular "limitations" in mind? Besides freespace(1) , I can't think of anything (1) which I'd argue is out-of-scope for anything digikam-specific. if you're out-of-space, all bets are off anyway, not much of anything will work reliably.
My intention is, to level didiKam to even more on a proffessional stage. In this context, waste of time, reliability and avoiding of inefficient proceedings is crucial. OK, you are right, one needs to clarify, what is really "crucial". "Space" is an issue: if you do panoramas, you'll need lot of space intermediately. Why not show a warning, _before_ you waste time? I guess, it is possible, to derive a rule of thumb for estimate the needed space ("number x pic size x safety factor", e.g.). Even when servicing your pics database, you need some more space for temp files than under regular working conditions. Why not warn, before loosing time or experiencing crashing progs? "Limitations": I am thinking of progs which check availability of libraries on demand (K3B, e.g.). If installed, the prog itself more features than "standard" installation with restricted abilities. "Limitations" in another sense, too: I'd like to have all pics in statistic, and I'd like to distingish between the ones digiKam can open and the ones, which digiKam can NOT open ("broken ones"?. Background: I have some hundreds of NEF, digiKam can not open at all It would be most helpful to search and find for those, as one might have backups, could be able to reapit questioned files etc. Axel --- Am 16.02.2013 18:52, schrieb Rex Dieter: > https://bugs.kde.org/show_bug.cgi?id=315271 > > Rex Dieter <rdieter@math.unl.edu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |rdieter@math.unl.edu > > --- Comment #1 from Rex Dieter <rdieter@math.unl.edu> --- > Did you have any particular "limitations" in mind? > > Besides freespace(1) , I can't think of anything > > (1) which I'd argue is out-of-scope for anything digikam-specific. if you're > out-of-space, all bets are off anyway, not much of anything will work reliably. >
*** Bug 413839 has been marked as a duplicate of this bug. ***