https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #75 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #74)
> If a build with this commit is available, you will need to recreate the
> temporary Google Maps HTML file. This can be achieved when the key is
> changed, i.
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #66 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #65)
> No, there is no setting for this. I suspect it has something to do with the
> graphics acceleration of the QWebEngine. I also have a desktop computer with
> W
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #64 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #63)
> I have no problems with the markers in the Windows version, they are
> displayed.
>
> Maik
Are there any settings that can be used to influence t
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #62 from Kurpfaelzer ---
(In reply to caulier.gilles from comment #61)
> Hi Kurpfaelzer,
>
> This is a great advance in this file. Great...
>
> For your test about the pending image position problem over GoogleMaps, i
>
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #60 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #59)
> With one of the next test versions you can use DebugView to see why the key
> is probably not accepted.
> Alternatively, you could provide me with your key fo
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #57 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #56)
> @Kurpfaelzer, Have you also set up a billing account? The API key that you
> could create 2 years ago is now not valid without a payment option.
> Maik
Hi Ma
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #55 from Kurpfaelzer ---
(In reply to caulier.gilles from comment #54)
> Hi all ,
>
> With 8.2.0, digiKam is not cross compiled anymore. The build is native under
> Windows 10 and Google maps must work fine under Windows with
https://bugs.kde.org/show_bug.cgi?id=318965
--- Comment #4 from Kurpfaelzer ---
Thx
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=318965
Kurpfaelzer changed:
What|Removed |Added
CC||stephan.kr...@t-online.de
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=473450
--- Comment #10 from Kurpfaelzer ---
Hello all,
First of all, I would like to thank Maik and Gilles very much for searching
intensively and quickly for a solution to this problem.
I have now installed the new version 8.2 from today.
Unfortunately
https://bugs.kde.org/show_bug.cgi?id=473450
Kurpfaelzer changed:
What|Removed |Added
CC||stephan.kr...@t-online.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=469781
Bug ID: 469781
Summary: Neither a marker nor a thumbnail are displayed in the
map view with GoopleMaps
Classification: Applications
Product: digikam
Version: 8.1.0
Platform:
https://bugs.kde.org/show_bug.cgi?id=467090
--- Comment #9 from Kurpfaelzer ---
Thank you for your efforts to solve the problem.
If I understand correctly, then the use of Google Maps is no longer possible
for the time being?
I would like to refer you once again to the "GeoSetter"
https://bugs.kde.org/show_bug.cgi?id=467090
Bug ID: 467090
Summary: Maps Window with Google Maps only empty
Classification: Applications
Product: digikam
Version: 8.0.0
Platform: Other
OS: Microsoft Windows
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #43 from Kurpfaelzer ---
@Erik: thank you for the explanatory note. I am not familiar with the topic now
and therefore cannot classify it. But would that possibly be a way for Digikam?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #41 from Kurpfaelzer ---
Just a short question:
What is the difference between Geosetter and Digikam when using google.maps?
In the new beta of Geosetter you can use google.maps without the rather
annoying note "for development pur
https://bugs.kde.org/show_bug.cgi?id=462807
--- Comment #3 from Kurpfaelzer ---
(In reply to caulier.gilles from comment #1)
> Which digiKam version did you use exactly ?
>
> Which operating system ?
>
> Gilles Caulier
I'm currently using "digiKam-7.10.0-20221207T08482
https://bugs.kde.org/show_bug.cgi?id=462807
Bug ID: 462807
Summary: How to show GPS-Tracks in addition to geotagged
photos in Maps view
Classification: Applications
Product: digikam
Version: unspecified
Platform:
https://bugs.kde.org/show_bug.cgi?id=460779
Kurpfaelzer changed:
What|Removed |Added
CC||stephan.kr...@t-online.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=455805
--- Comment #3 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #2)
> The mentioned change of reading the current database encoding is actually
> not included in digiKam-7.7.0.
> However, a long-standing Qt bug that always returne
https://bugs.kde.org/show_bug.cgi?id=455805
Bug ID: 455805
Summary: At start of digikam: "Your locale has changed since
this album was last opened."
Product: digikam
Version: 7.7.0
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=445424
--- Comment #9 from Kurpfaelzer ---
Hi Maik,
thank you for your explanation.
Now I know, that the location properties are stored in the
"ImageProperties"-table, but so far there is no option to use them in DigiKam.
But it would be a worthf
https://bugs.kde.org/show_bug.cgi?id=445424
--- Comment #7 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #6)
> You don't have to add all of the address elements. You can add individual
> address elements that you need, also at the point in the tag tree
https://bugs.kde.org/show_bug.cgi?id=445424
--- Comment #5 from Kurpfaelzer ---
More or less, yes.
For example:
I have a phot, which was taken at:
49,41962673 / 8,70417465
The location I got from GeoSetter (Geonames) are:
Primary Location Name: Deutschland
Province-State: Baden-Württemberg
https://bugs.kde.org/show_bug.cgi?id=445424
--- Comment #4 from Kurpfaelzer ---
Created attachment 143513
--> https://bugs.kde.org/attachment.cgi?id=143513=edit
pic 3
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=445424
--- Comment #3 from Kurpfaelzer ---
Created attachment 143512
--> https://bugs.kde.org/attachment.cgi?id=143512=edit
pic 2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=445424
--- Comment #2 from Kurpfaelzer ---
Created attachment 143511
--> https://bugs.kde.org/attachment.cgi?id=143511=edit
pic 1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=445424
Bug ID: 445424
Summary: Reverse Geocoding - Using GeoTags from Geosetter
Product: digikam
Version: unspecified
Platform: Other
OS: Other
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=443818
--- Comment #2 from Kurpfaelzer ---
Thx for your quick response!
Stephan
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443818
Bug ID: 443818
Summary: Last modified files on https://files.kde.org/digikam/
are dated 2021-09-05
Product: digikam
Version: unspecified
Platform: Other
OS: Other
https://bugs.kde.org/show_bug.cgi?id=441521
Bug ID: 441521
Summary: Where to find package called digikam-doc?
Product: digikam
Version: unspecified
Platform: Other
OS: Other
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #5 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #2)
> From March 1st, the Google Maps map will work again.
>
> Maik
Is there another issue with Google Maps or why does the label still appear?
Stephan
--
You are
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #3 from Kurpfaelzer ---
Thank you for your clarification!
Stephan
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433732
--- Comment #1 from Kurpfaelzer ---
In the meantime, I found following discussion:
https://mail.kde.org/pipermail/digikam-users/2021-February/031925.html
"Hi all
this morning I wanted to modify the geolocalisation of my latest
pictures , and w
https://bugs.kde.org/show_bug.cgi?id=433732
Kurpfaelzer changed:
What|Removed |Added
Summary|Google Maps labeled "For|Google Maps lab
https://bugs.kde.org/show_bug.cgi?id=433732
Bug ID: 433732
Summary: Google Maps labeled "For development purposes only"
Product: digikam
Version: 7.2.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status:
https://bugs.kde.org/show_bug.cgi?id=433432
Bug ID: 433432
Summary: Updated documentation about Face-Tagging
Product: digikam
Version: 7.2.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=431598
--- Comment #4 from Kurpfaelzer ---
It works.
Thank you for your debugging and quick bug fixing!
Stephan Kranz
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431598
--- Comment #2 from Kurpfaelzer ---
(In reply to caulier.gilles from comment #1)
> Please use the windows installler including debug symbols and when it crash
> provide a backtrace.
>
> https://files.kde.org/digikam/digiKam-7.2.0-rc-202
https://bugs.kde.org/show_bug.cgi?id=431598
Bug ID: 431598
Summary: digikam 7.2.0-rc (14.01.2021) crashes while getting
"Help > List of Detected Hardware"
Product: digikam
Version: 7.2.0
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=429335
--- Comment #5 from Kurpfaelzer ---
The problem has been solved. THX to all.
Stephan
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429335
Bug ID: 429335
Summary: digikam 7.2.0-beta2 (18.11.2020) crashes after
assigning name to unknown face
Product: digikam
Version: 7.2.0
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #23 from Kurpfaelzer ---
Hurra! It works. The GUI shows the (expected) behaviour.
Many thanks for the workaround and your kind assistance.
Great work.
Have a nice weekend!
Stephan
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #21 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #20)
> You are far too fast. ((:-)) I will only program the changes in the code in
> 2 hours and tomorrow new bundles will be available.
>
> Maik
Ähhh, sorry
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #19 from Kurpfaelzer ---
Created attachment 127992
--> https://bugs.kde.org/attachment.cgi?id=127992=edit
Environment
Thank you for the new version.
After installing the program, I proceeded as you described in your comment:
I ad
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #18 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #16)
> The change (see comment 6) was added on March 1st. Gilles probably didn't
> create any new bundles for a few days. This change is definitely the cause.
> If yo
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #15 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #13)
> We have added
> "qputenv("QT_AUTO_SCREEN_SCALE_FACTOR","1") so that Qt adapts to the scaling
> factor of Windows.
But this has
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #11 from Kurpfaelzer ---
https://bugs.kde.org/show_bug.cgi?id=398582#c9
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #10 from Kurpfaelzer ---
Attached you will find the settings for my TV-screen.
But nevertheless, all versions before including the beta3-version mentioned in
my starting post had no problems with these settings.
Probably you changed some
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #9 from Kurpfaelzer ---
Created attachment 127964
--> https://bugs.kde.org/attachment.cgi?id=127964=edit
Settings for the TV-screen
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #7 from Kurpfaelzer ---
I'm using a resolution of 1920 x 1080 as recommended by my system.
Stephan
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #5 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #3)
> The behavior is normal, the GUI must scale if you have set 150% under
> Windows. This is the prerequisite that digiKam is not too "small" on a HiDPI
&
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #4 from Kurpfaelzer ---
(In reply to Maik Qualmann from comment #3)
> The behavior is normal, the GUI must scale if you have set 150% under
> Windows. This is the prerequisite that digiKam is not too "small" on a HiDPI
>
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #2 from Kurpfaelzer ---
Created attachment 127962
--> https://bugs.kde.org/attachment.cgi?id=127962=edit
DigiKam-7-RC-100.jpg
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420727
--- Comment #1 from Kurpfaelzer ---
Created attachment 127961
--> https://bugs.kde.org/attachment.cgi?id=127961=edit
DigiKam-7-RC.jpg
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420727
Bug ID: 420727
Summary: digiKam-Window and all Sub-Windows are enlarged too
much
Product: digikam
Version: 7.0.0
Platform: unspecified
OS: MS Windows
https://bugs.kde.org/show_bug.cgi?id=399336
--- Comment #2 from Kurpfaelzer ---
Thank you for your quick and very helpful answer.
By replacing the html-file digiKam-5.9.0 works with Google Maps again.
Great!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399336
Bug ID: 399336
Summary: Google maps – "For development purposes only" printed
on the map
Product: digikam
Version: 5.9.0
Platform: MS Windows
OS: MS Windows
https://bugs.kde.org/show_bug.cgi?id=392090
Bug ID: 392090
Summary: While scanning collection the progess bar shows 0%
Product: digikam
Version: 5.9.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=392088
Kurpfaelzer <stephan.kr...@t-online.de> changed:
What|Removed |Added
Summary|digikam loses DB content|digikam lo
https://bugs.kde.org/show_bug.cgi?id=392088
Bug ID: 392088
Summary: digikam loses DB content after power savin mode of
Win10
Product: digikam
Version: 5.9.0
Platform: MS Windows
OS: MS Windows
https://bugs.kde.org/show_bug.cgi?id=375317
--- Comment #3 from Kurpfaelzer <stephan.kr...@t-online.de> ---
Unfortunattely, digikam still crashes during face recognition.
But I'm no longer sure whether this behavior really depends on MYSQL.
For version 5.6 (incl. pre-releases) I realized a
https://bugs.kde.org/show_bug.cgi?id=380805
--- Comment #14 from Kurpfaelzer <stephan.kr...@t-online.de> ---
@all:
THX a lot. The creation of a HTML Gallery is currently working without deleting
any other directories or files within the target directory.
Thank you for your great work.
https://bugs.kde.org/show_bug.cgi?id=380805
--- Comment #12 from Kurpfaelzer <stephan.kr...@t-online.de> ---
@Gilles:
just a short question: have you had a chance already to check Maiks fixes and
to rebuild the windows installer? If so, I would try out the fix in a sandbox
whether it wil
https://bugs.kde.org/show_bug.cgi?id=380805
--- Comment #10 from Kurpfaelzer <stephan.kr...@t-online.de> ---
The original pictures are placed in directory X:\
The output directory was set to : C:\Users\x\Pictues\
Everything which was placed in this output directory before was d
https://bugs.kde.org/show_bug.cgi?id=380805
--- Comment #7 from Kurpfaelzer <stephan.kr...@t-online.de> ---
Many thanks for your correction.
The Gallery vould be cerated and it works!
BUT
All files and folders within the specified directory are obviously deleted
before.
Because I sp
https://bugs.kde.org/show_bug.cgi?id=380805
--- Comment #4 from Kurpfaelzer <stephan.kr...@t-online.de> ---
Thank you for your quick answer.
Indeed, it seems that the description of the path is wrong. Not onyl the slash
in front of the drive letter, but also the double-slash before the xs
https://bugs.kde.org/show_bug.cgi?id=380805
Kurpfaelzer <stephan.kr...@t-online.de> changed:
What|Removed |Added
Platform|Other |MS Windows
-
https://bugs.kde.org/show_bug.cgi?id=380805
Bug ID: 380805
Summary: Generating Gallery: "Could not load XSL file"
Product: digikam
Version: 5.6.0
Platform: Other
OS: MS Windows
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=371485
--- Comment #6 from Kurpfaelzer <stephan.kr...@t-online.de> ---
In digikam 5.4 the Titanic museum can be seen on the corresponding google maps
view. Don't know why, but this is perfect for me. Hope that is valid for other
locations as well.
S
https://bugs.kde.org/show_bug.cgi?id=375317
Bug ID: 375317
Summary: MYSQL: digikam crashes during face recognition
Product: digikam
Version: 5.4.0
Platform: Compiled Sources
OS: MS Windows
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=371485
--- Comment #4 from Kurpfaelzer <stephan.kr...@t-online.de> ---
Created attachment 101705
--> https://bugs.kde.org/attachment.cgi?id=101705=edit
Google Maps / Titanic Belfast - Web-Browser view
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=371485
--- Comment #3 from Kurpfaelzer <stephan.kr...@t-online.de> ---
Created attachment 101704
--> https://bugs.kde.org/attachment.cgi?id=101704=edit
Google Maps / Titanic Belfast - digikam view
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=371485
--- Comment #2 from Kurpfaelzer <stephan.kr...@t-online.de> ---
I don't know whether digikam can control that or not.
To give you an idea concerning the difference between a satelite pic within
digikam and the same position within a browser
https://bugs.kde.org/show_bug.cgi?id=371485
Bug ID: 371485
Summary: GoogleMaps outdated
Product: digikam
Version: 5.2.0
Platform: Other
OS: other
Status: UNCONFIRMED
Severity: wishlist
Priority:
75 matches
Mail list logo
