Bug 333630 - Cannot search items with exposure times > 30s or focal lengths > 1000mm
Summary: Cannot search items with exposure times > 30s or focal lengths > 1000mm
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Advanced (show other bugs)
Version: 3.5.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-19 17:52 UTC by jackbak1
Modified: 2017-08-18 09:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.11.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jackbak1 2014-04-19 17:52:18 UTC
Using astro photos need to be able to search on Exifs that contain long exposures and/or long focal lengths 254mm Newtonian at f4 = 1016mm

Reproducible: Always

Steps to Reproduce:
1. Try the search I've described above
2.
3.
Actual Results:  
no search results even though individual photos have valid and correct Exifs
Comment 1 caulier.gilles 2015-05-16 14:11:24 UTC
Maik,

Another entry very simple to implement, as high ranges just need to be changed in Advanced Search tool GUI.

Gilles
Comment 2 Maik Qualmann 2015-05-24 11:04:04 UTC
Gilles,

The maximum exposure time can be set to 24 hours and focal lenght to 200000mm. Perhaps the problem is, that left the longer exposure time and right the shorter exposure time is set. Similarly, the exposure time is increased at lower button. This inverted attitude to the exposure time is quite common in some camera models. But I think the direction of a number line from left (negative) to the right (positive) logical.

Maik
Comment 3 caulier.gilles 2015-05-24 11:32:36 UTC
Maik, thanks to review...

So, if i understand, the original wish from this report is fixed since a while...

As the GUI behavior sound like logical (tested here), this entry can be closed as fixed now. No need to left an entry open as well. If something still wrong, user can re-open the file later or create a new one (we need a good visibility over all reports in bugzilla).

Gilles