digikam 2.6 beta 2 in any part of digikam (gpssync, right panel, center panel) openstreetmap maps by default are blur marble has solved the pb see bug #199259 but to have non blur map you must applies these principles in marble and in digikam : - use only "mercator" - use only buttons + and - to zoom thus don't use mouse wheel consequently i suggest : - when selecting openstreetmap then by default "mercator" is selected - when selecting openstreetmap mouse wheel movements are translated to + or - button clicks or at least when selecting openstreemap then ahelp windows pops up saying "you must use mercator and +- buttons to have a non blur map" thanks addendum : i don't remember where i read this but marble devs plan to build a bank of vectorized (svg) osm maps thus a kde server for this.
Can you provide a screesnhoot of the problem please ? Gilles Caulier
Created attachment 69668 [details] blur rmap
Created attachment 69669 [details] non blur map
i remeber with previous versions i can choose the horizontal size of the windows as any type of kde windows for example the digikam window
ignore comment #4
This file still valid using digiKam 3.5.0 ? Gilles Caulier
opensuse 13.1 , kde 4.12 , digikam 3.5 Samsung Galaxy SII P , android 4.2.2 still valid
What's about this file using last digiKam 4.2.0 ? Gilles Caulier
opensuse 13.1 , kde 4.14.0 , digikam 4.2.0 bug still valid
Michael, Can we considerate this bug as fully relevant of Marble widget ? Gilles
Gilles, I do not know for sure, have to check the API. Michael
Micheal, This bug is relevant of libkgeomap or marble ? Gilles
Philippe, Problem still here using last digiKam 4.9.0 ? Gilles Caulier
Hi Gilles, I think this is a Marble problem, and can be solved by following the steps outlined in #199259 as Philippe pointed out, namely using the Mercator projection and only using Marble's zoom buttons for zooming in/out. Other than that, there is nothing we can do, unless we want to define special keyboard shortcuts. Then, however, usage of Marble inside digikam would be different from normal Marble... Michael
kde app 18.12.2 kde plasma 5.15.2 kde framework 5.55.0 qt 5.12.1 digikam 6.0.0 marble 2.2.20 problem still there.
Philippe, is this a duplicate of bug 199259?
(In reply to Christoph Feck from comment #16) > Philippe, is this a duplicate of bug 199259? if this is a marble problem then yes. at hte beginning this report is about digikam.