[Digikam-devel] [Bug 205001] MapSearch: Merge overlapping markers to clusters
Michael G. Hansen
mhansen at mghansen.de
Mon Sep 7 20:26:32 BST 2009
https://bugs.kde.org/show_bug.cgi?id=205001
Michael G. Hansen <mhansen at mghansen.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #36651|0 |1
is obsolete| |
--- Comment #24 from Michael G. Hansen <mhansen mghansen de> 2009-09-07 21:26:27 ---
Created an attachment (id=36777)
--> (http://bugs.kde.org/attachment.cgi?id=36777)
Map clustering, new version
new version:
- instant popup of map theme menu
- thumbnails for clusters with multiple images
- thumbnails configurable through map theme menu
- shows selected search area on the map
Question:
Should the map search by updated when the user deletes/moves/rates images?
Currently it does not, and also the Timeline-search does not update, either.
Gilles:
We can show the selected search area now. It is stored as a rectangle
internally, but when drawn on the map, it can look like a trapezoid depending
on the projection. This might be confusing to some users, but I do not know a
better solution.
Mikolaj:
Thanks for the new description and the screenshot, I understand the problem
now. But I do not know yet how to solve it exactly. When not using geosearch,
and you use the mime-type filter, and go for example from "JPEG Files" to "PNG
Files" while in preview mode, the problem does not occur. I do not know yet
where the clustering code's interaction with the filters is different for the
mime-type code.
Arnd:
Does the preview of multiple images come close to what you suggested?
left to do:
- adjust indentation in markerclusterholder-files to digikam coding guidelines,
it was reset somehow
- find a way to set a bounding box on Marble
- update the map search when images in the database are changed
- solve problem with previewed images in the main view when clusters are
changed
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Digikam-devel
mailing list