Bug 244701 - map search tool selects a whole hemisphere when trying to select large areas
Summary: map search tool selects a whole hemisphere when trying to select large areas
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Map (show other bugs)
Version: 1.4.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-15 09:12 UTC by Gandalf Lechner
Modified: 2012-06-27 10:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 2.0.0
Sentry Crash Report:


Attachments
screenshot showing the wrong map selection (274.49 KB, image/png)
2010-07-15 09:12 UTC, Gandalf Lechner
Details
screenshot showing the right map selection when using a smaller selection area (303.42 KB, image/png)
2010-07-15 09:12 UTC, Gandalf Lechner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gandalf Lechner 2010-07-15 09:12:06 UTC
Created attachment 49164 [details]
screenshot showing the wrong map selection

Version:           1.4.0 (using KDE 4.4.4) 
OS:                Linux

when dragging a rather large selection box in the map search tool, it often does not select the desired area, but a larger area instead. as an example, see the attached screenshot. here i put a box around australia (grey rectangle), but the returned selection apparantly is the whole southern hemisphere; it for sure returned pictures located in southern africa and america. see the blue line going straight up from the south pole.

it seems to me that this problem only shows up when the selection box is quite big (as australia). when selecting a smaller area, everything works as expected, see second screenshot.

Reproducible: Sometimes




OS: Linux (x86_64) release 2.6.32-24-generic
Compiler: cc
Comment 1 Gandalf Lechner 2010-07-15 09:12:46 UTC
Created attachment 49165 [details]
screenshot showing the right map selection when using a smaller selection area
Comment 2 Marcel Wiesweg 2011-01-20 16:58:56 UTC
I believe this is fixed for 2.0.
Comment 3 caulier.gilles 2011-01-20 17:07:59 UTC
Yes, i think so, i cannot reproduce the problem here.

Michael, can you confirm ?

Gilles Caulier
Comment 4 Gabriel Voicu 2011-01-20 23:31:44 UTC
Yes, it's fixed in 2.0.